Thanks for the bug report! I've fixed this issue in v0.2.1 which should be available now (here's the changelog).
