Closed vincent-ferotin closed 5 years ago
Seems strange that it succeeded with Yarn but not with NPM, did you try NVM to setup your Node env?
Sometimes it might also just be an npm cache corruption, using npm cache clean --force
usually solves these kind of issues.
Anyways, it doesn't hurt to mention alternatives so I welcome this PR, I just fixed the Yarn command to be global like NPM 😉
I think my different tries of installations of NPM were somehow broken, and that precisely would disallow usage of global install (-g
option). I'm very unfamiliar with NodeJS and its ecosystem, so this is a guess rather than a certainty...
Ah yes, most package install (and even the install from node.js website) needs admin rights for global packages, which is an issue. But this can be fixed easily by manually setting the global package folder to an user folder: https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally
Yarn does not have this issue (even with global) because its cache and installed packages always goes in the user home folder.
Hi Yohan,
I'd tried to install, for testing, backslide with NPM and failed miserably (Ubuntu 19.04, NodeJS 10, NPM 6.9), but had some success with Yarn. So I decided to list it as an alternative to NPM in both README and https://sinedied.github.io/backslide/ .
Please feel free to pull this small change, adapt it, rewrite it all, or ignore it ;-)
V.F.