Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NPMv3: Non-deterministic dependency tree - avoid by appending version number to folder name #4503

Closed
SetTrend opened this issue Dec 31, 2015 · 1 comment
Labels
npm Issues and PRs related to the npm client dependency or the npm registry.

Comments

@SetTrend
Copy link

The current situation of non-deterministic folder structure in NPM v3 isn't satisfying. Depending on the installation order, deep nested directory structures may still occur.

I suggest to append the version to the package name, then all packages may be installed into the same directory:

$ tree -d node_modules/
node_modules/
|-- mod-a@1.0.0
|-- mod-b@1.0.0
|-- mod-b@2.0.0
|-- mod-c@1.0.0

from

$ npm install
|-- mod-a@1.0.0
| |-- mod-b@1.0.0
|-- mod-c@1.0.0
| |-- mod-b@2.0.0
@cjihrig
Copy link
Contributor

cjihrig commented Dec 31, 2015

Please raise questions related to npm at https://github.com/npm/npm.

@cjihrig cjihrig closed this as completed Dec 31, 2015
@ChALkeR ChALkeR added npm Issues and PRs related to the npm client dependency or the npm registry. invalid Issues and PRs that are invalid. and removed invalid Issues and PRs that are invalid. labels Jan 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
npm Issues and PRs related to the npm client dependency or the npm registry.
Projects
None yet
Development

No branches or pull requests

3 participants