5 ms·

Could you expand on that? What causes it to be nondeterministic? I haven't had that experience but it's the second time I've read someone reference this behavio

by krisdol 11y ago

Could you expand on that? What causes it to be nondeterministic? I haven't had that experience but it's the second time I've read someone reference this behavior

yunong 11y ago
I have a project that's shrinkwrapped. I check out a new copy of the project and run `npm install`. My co-worker does the exact same thing, his fails, yet mine successfully builds. An install of a shrink-wrapped should be deterinistic, i.e. either succeed or fail, but not both.
- Wintamute 11y ago
  From that doc page it sounds like that should be deterministic? Even without shrinkwrapping, a fresh install from package.json with empty node_modules should be deterministic. > The npm install command, when used exclusively to install packages from a package.json, will always produce the same tree. This is because install order from a package.json is always alphabetical. Same install order means that you will get the same tree. > You can reliably get the same dependency tree by removing your node_modules directory and running npm install whenever you make a change to your package.json. Maybe you're experiencing a bug, rather than some in-grained non-determinism in npm?
  - madeofpalk 11y ago
    My understanding is that even when you fix your dependencies to exact versions, your dependencies probably haven't so without shrink-wrap you'll never know _exactly_ what gets installed.
- kemitchell 11y ago
  What's the error on the build that fails?
dandelany 11y ago
Here are details from the docs: https://docs.npmjs.com/how-npm-works/npm3-nondet https://docs.npmjs.com/how-npm-works/npm3-nondet
- kemitchell 11y ago
  > You can reliably get the same dependency tree by removing your node_modules directory and running npm install whenever you make a change to your package.json. https://docs.npmjs.com/how-npm-works/npm3-nondet https://docs.npmjs.com/how-npm-works/npm3-nondet
  - krisdol 11y ago
    That explains why I haven't experienced it -- our projects' npm scripts to build packages wipe out that folder before building.

by krisdol 11y ago

Could you expand on that? What causes it to be nondeterministic? I haven't had that experience but it's the second time I've read someone reference this behavior

yunong 11y ago

I have a project that's shrinkwrapped. I check out a new copy of the project and run `npm install`. My co-worker does the exact same thing, his fails, yet mine successfully builds. An install of a shrink-wrapped should be deterinistic, i.e. either succeed or fail, but not both.

Wintamute 11y ago
From that doc page it sounds like that should be deterministic? Even without shrinkwrapping, a fresh install from package.json with empty node_modules should be deterministic. > The npm install command, when used exclusively to install packages from a package.json, will always produce the same tree. This is because install order from a package.json is always alphabetical. Same install order means that you will get the same tree. > You can reliably get the same dependency tree by removing your node_modules directory and running npm install whenever you make a change to your package.json. Maybe you're experiencing a bug, rather than some in-grained non-determinism in npm?
- madeofpalk 11y ago
  My understanding is that even when you fix your dependencies to exact versions, your dependencies probably haven't so without shrink-wrap you'll never know _exactly_ what gets installed.
kemitchell 11y ago
What's the error on the build that fails?

dandelany 11y ago

Here are details from the docs: https://docs.npmjs.com/how-npm-works/npm3-nondet https://docs.npmjs.com/how-npm-works/npm3-nondet

kemitchell 11y ago
> You can reliably get the same dependency tree by removing your node_modules directory and running npm install whenever you make a change to your package.json. https://docs.npmjs.com/how-npm-works/npm3-nondet https://docs.npmjs.com/how-npm-works/npm3-nondet
- krisdol 11y ago
  That explains why I haven't experienced it -- our projects' npm scripts to build packages wipe out that folder before building.