Closed egel closed 7 years ago
Hi @egel,
This may have been introduced during the somewhat circuitous way I merged #37.
I'll take a look tonight. Danke!
This is normal.
As we can see from the pull request on #37, it is tagged as the 0.1.4 milestone, which will be released shortly and which is (currently) synchronized with master
.
Thanks!
There is some incoherence in returning api methods between
master
branch and latest tagv0.1.3
(for the moment of writing).Creating new tag version according to master & update npm packages should resolve the problem.