Closed julien-c closed 7 years ago
PS: I can confirm that the issue is with npm 5, not node 8.
If I fix it, any way this can be merged quickly? (forked npm modules are a pain to setup in a project...)
@julien-c have you found a solution for the problem ?
Nope, no reply from @moos so far
Installing with yarn
instead of npm
works fine for a quick workaround!
I made an issue here: npm/npm#17073
Yay thanks for the investigation @benhjames great job!
Sorry for belated reply -- and thanks for investigating and filing the issue on npm 5. Not sure how I can unblock anyone running into this issue. Let's hope npm folks will issue a patch soon.
Maybe in the meantime ship a untarred version of wordnet-db
, or temporarily link to my fork as a dependency? https://github.com/julien-c/wordnet-db
(Seems like lots of people here rely on your package for production systems :)
After a failed attempt at polling for the wordnet-db dict/ folder, I've gone with @julien-c's recommendation of checking in the exploded dict/ files in wordnet-db until there is a fix for npm.
Please try re-installing.
Yes, worked well.
Thanks.