varac
commented
7 years ago I encountered this installing a list of dependencies. It went away when i split the list of modules and ran two separate commands. I think we should do the same. Looks like the easiest solution so far. If somebody comes up with a sane split of modules list I'm happy to give it another try, because sshfs seems to be the filesystem when it breaks unrecoverably.
Not sure, If I understood the solution. How can we split the list of modules, if they are all in the package.json?
Unfortunatly, npm doesn't let you add your custom package groups, like i.e. bundler for ruby handle it.
But we could start splitting packages into dependencies and devdependencies.
I.e.:
dependencies: All modules needed for getting the useragent up and running from sourcedevdependencies: All modules needed for running tests etc.
from https://docs.npmjs.com/cli/install: "With the --production flag (or when the NODE_ENV environment variable is set to production), npm will not install modules listed in devDependencies."
We could first install the dependencies with npm install --production and after that the devdependencies with npm install
tayanefernandes
The rationale behind this is that we now a too complex dependency graphs of node modules (~1000 !). This breaks at least under certain circumstances like installing the modules on a shared folder inside vagrant.