I insist, this is fixed in version v0.0.5, thanks to your very warning.