3 ms·

NPM 5.x in Node v8.1 consistently only installs 481 out of 493 packages in our node_modules folder. No errors, everything looks absolutely fine, except 12 packa

NPM 5.x in Node v8.1 consistently only installs 481 out of 493 packages in our node_modules folder. No errors, everything looks absolutely fine, except 12 packages are straight up missing. That was fun to debug! Both NPM 3 and yarn produce the expected result. That was the last straw for me and NPM is now banned in favor of yarn.

deleted 9y ago
[deleted]
Muuuchem 9y ago
Lol mine has been oddly adding 1000 packages only sometimes when I npm install after a pull when we are using maybe 100 shits weird.
mAritz 9y ago
Same thing happened to me in multiple projects on multiple machines. Weird how that seems so common and still made it into v5.
deleted 9y ago
[deleted]
whatever_dude 9y ago
I actually had the opposite happening: a project was having some real issues with not installing proper dependencies until we started using npm 5.3+. Things work fine now and are a bit more deterministic it seems. It's an odd project with a lot of super strange peer dependencies, many of them in beta or as pre-releases, so I'm sure it's nothing that happens all the time (the joys of using React Native and Relay where everything is at an imaginary release state). But still glad npm 5 made it work consistently.
- hinkley 9y ago
  Same. One team is running npm@3 installs twice in CI to pick up half a dozen modules that don't install the first time. On another project I managed to massage the package.json to stop it from happening.
AgentME 9y ago
Do you any dependencies or subdependencies with git urls? I've previously run into https://github.com/npm/npm/issues/17189 https://github.com/npm/npm/issues/17189, and I solved it by ... updating the dependency to a newer version that switched away from having subdependency pulled from git.
- AgentME 9y ago
  Good news, I just looked at that bug again and it turns out it's no longer reproducible in the latest version of npm.
tracker1 9y ago
I find less issues when I `rm -rf node_modules`, `rm package-lock.json` and `npm i` again... usually when I manually edit my package.json packages.

deleted 9y ago

[deleted]

Muuuchem 9y ago

Lol mine has been oddly adding 1000 packages only sometimes when I npm install after a pull when we are using maybe 100 shits weird.

mAritz 9y ago

Same thing happened to me in multiple projects on multiple machines. Weird how that seems so common and still made it into v5.

deleted 9y ago

[deleted]

whatever_dude 9y ago

I actually had the opposite happening: a project was having some real issues with not installing proper dependencies until we started using npm 5.3+. Things work fine now and are a bit more deterministic it seems. It's an odd project with a lot of super strange peer dependencies, many of them in beta or as pre-releases, so I'm sure it's nothing that happens all the time (the joys of using React Native and Relay where everything is at an imaginary release state). But still glad npm 5 made it work consistently.

hinkley 9y ago
Same. One team is running npm@3 installs twice in CI to pick up half a dozen modules that don't install the first time. On another project I managed to massage the package.json to stop it from happening.

AgentME 9y ago

Do you any dependencies or subdependencies with git urls? I've previously run into https://github.com/npm/npm/issues/17189 https://github.com/npm/npm/issues/17189, and I solved it by ... updating the dependency to a newer version that switched away from having subdependency pulled from git.

AgentME 9y ago
Good news, I just looked at that bug again and it turns out it's no longer reproducible in the latest version of npm.

tracker1 9y ago

I find less issues when I `rm -rf node_modules`, `rm package-lock.json` and `npm i` again... usually when I manually edit my package.json packages.