Skip to content
This repository has been archived by the owner before Nov 9, 2022. It is now read-only.

npm behaves non-deterministically wrt to dependencies that are already installed #5655

mgol opened this issue Jul 9, 2014 · 2 comments


Copy link

mgol commented Jul 9, 2014

Step to reproduce (the grunth-cli package depends on grunt-cli):

  1. npm -g i grunt-cli
  2. npm -g i grunth-cli
  3. npm -g i grunth-cli

After (1-2), the structure is:

├── grunt-cli
├── grunth-cli

After (1-3):

├── grunt-cli
├─┬ grunth-cli
  ├── grunt-cli

This is with npm 1.4.20, Node both 0.10.29 and 0.11.13.

@othiym23 othiym23 added the bug label Sep 18, 2014
@othiym23 othiym23 modified the milestones: cache rewrite, multi-stage install Sep 18, 2014
Copy link

smikes commented Nov 19, 2014

Is this still a problem for you?

When I try to reproduce this with latest npm, I find that grunt-cli is installed both at the global level and as a dependency of grunth-cli after step 2 only. Step 3 causes no change.

I tested this with

$ mkdir foo
$ npm --prefix=foo i -g grunt-cli
$ npm --prefix=foo i -g grunth-cli
$ npm --prefix=foo ls -g 
$ npm --prefix=foo i -g grunth-cli
$ npm --prefix=foo ls -g 

We are trying to clean up older npm issues, so if we don't hear back from you within a week, we will close this issue. (Don't worry -- you can always come back again and re-open it!)


Copy link

mgol commented Nov 25, 2014

I cannot reproduce it either anymore. It seems one of 2.x.y releases fixed it.

@mgol mgol closed this as completed Nov 25, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet

No branches or pull requests

3 participants