4 ms·

The lack of activity in the issue is sadly not rare for npm.

• AgentME 10y ago
  Yeah, I reported https://github.com/npm/npm/issues/10463 https://github.com/npm/npm/issues/10463 (npm fails to install everything from a shrinkwrap sometimes -- the feature specifically for locking down the dependencies to make things deterministic/reproducible!) about a year ago and it hasn't received much attention. It was labeled "big-bug" once but got downgraded to "support" somewhere along the line. I use npm in a continuous integration/deployment system for a project. The system used to do a git checkout, `npm install` to get the dependencies, and then a build, but then we ran into a few extremely confusing issues where we actually had a couple old dependencies tested and deployed into production because npm install failed to respect the shrinkwrap fully (yet it still exited successfully). We finally had to write a script which compares the node_modules directory against the shrinkwrap, and if there's a mismatch, it removes the entire directory and re-runs `npm install`. Thankfully `npm install` tends to install everything fine from a fresh slate, but it's just soo slow (which is also surprising to me, because shouldn't most everything be cached into ~/.npm if I've installed nearly all of the same dependencies recently? I would think that installing from a shrinkwrap of many things I've installed before would mostly be un-tarring things from cache)...
• labster 10y ago
  Not just npm. My umask bug in Firefox has just celebrated its fifth birthday. https://bugzilla.mozilla.org/show_bug.cgi?id=688944 https://bugzilla.mozilla.org/show_bug.cgi?id=688944
• doublerebel 10y ago
  Unfortunately I have noticed the same with multiple issues. Seems that's an organizational problem that yarn can't solve.