It might be related to a bug that will be patched in v0.2.1 in a moment, I'll verify. Thanks for letting me know.
