Hey @Spierek and anyone that reported this, Really sorry that such a trivial change took so long to land, and totally aware the package makes it worst. The fix is actually on its way in v2.0.2. The version is currently being QA-ed and contain several bug fixes and clean-up. So stay tuned, should be soon. Thanks for your patience !