This should be fixed in 0.0.26. Thanks for the report.