This issue has been identified and fixed with v0.2.1 which has been uploaded.
Apologies for any inconvenience
