This is known issue but I'll fix it in 1.0.6(I'm doing a major API upgrade). Sry for inconvenience.
no worries
