The npm community forum has been discontinued.
To discuss usage of npm, visit the GitHub Support Community.
Confused about dependency version resolution priority
I’m having an issue where the wrong version of
babel-core is ending up in the root
node_modules folder. Running
npm ls babel-core shows:
firstname.lastname@example.org /Users/<username>/projects/my-package ├─┬ email@example.com │ ├── firstname.lastname@example.org │ └─┬ email@example.com │ └─┬ firstname.lastname@example.org │ └─┬ email@example.com │ └── firstname.lastname@example.org deduped └─┬ email@example.com ├─┬ firstname.lastname@example.org │ ├── email@example.com │ └─┬ firstname.lastname@example.org │ ├─┬ email@example.com │ │ └── firstname.lastname@example.org deduped │ └─┬ email@example.com │ └── firstname.lastname@example.org deduped └─┬ email@example.com └── firstname.lastname@example.org
The version in the root folder
node_modules folder is
6.26.3 but I would have expected it to be
7.0.0-bridge.0 given that any package bringing it in is beneath one bringing in the higher version, but not knowing exactly what order the packages are installed in, I’m not sure if this assumption is correct or not.
Assuming npm is behaving correctly, other than specifying the desired version in
package.json, is there anyway I can have the version specified in
package.json installed at the root?
I have complete control to update the
build-scripts-xxx packages, but I do not want the dependency details to leak outside if possible. The reason for this is the whole point of these packages is to abstract away the tools used in maintaining the projects in a similar way that