npm: invalid package dependency#43
Conversation
|
Hi, Unfortunately they still haven't merged this into their master branch. Update: as mentioned in the linked PR, there is a fork supporting async evolution that also ported it to TypeScript. If the API is the same we can switch to that dependency. |
|
Oh, I didn't notice that the async functionality went missing. o_O Inspired by https://stackoverflow.com/a/33183255/6396693 one could actually reference the original branch instead of the PR (in this case the master branch of the fork from the PR-owner). As long as the maintainer doesn't remove it, it should be the same functionality working fine with Using the typescript version could in the long term also be interesting, this fix is definitely safer though and would, in the end, reenable npm-support instantaneously. :) |
|
i can confirm it also works with |
In #1 (comment) you mentioned that this should be fixed, but as of today this issue is still present when using
npm.