3 ms·

> The end result is identical Citation needed. Installing npm dependencies in different orders is not garanteed to be deterministic due to npm's package flatt

> The end result is identical Citation needed. Installing npm dependencies in different orders is not garanteed to be deterministic due to npm's package flattening and, before npm 8, plain broken dependency resolution strategy. The package-lock.json is essential to get the same mess that the initial developer got on the same order as his install. > and my local machine has a copy of that package somewhere too. On maven/gradle, like on pnpm, you get one copy of each library. Not 3000x copies of lodash spread around your disk.

nawgz 4y ago
> > The end result is identical > Citation needed. What do you mean? You cited it yourself: > Installing npm dependencies in different orders Fortunately, there is no difference in order between running it as a command and adding it and running `yarn install`, since you already had all the other packages locally either way. Anyways, these complaints are ridiculous, I'm sure I could dig into the past and find some broken Maven or Gradle resolutions. Let's see, 10 second time limit: > gradle.lockfile LOL wow. > 3000x copies of lodash spread around your disk LOL