-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Closed
Labels
Bugthing that needs fixingthing that needs fixing
Description
What / Why
When at least two levels of dependencies are present eg packageA -> packageB -> packageC, and are referenced by local path npm fails to find the reference to packageC and errors with eth following error:
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /home/chris/dev/npmCiLocalPath/packageC/node_modules/packageb/node_modules/packagea/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/home/chris/dev/npmCiLocalPath/packageC/node_modules/packageb/node_modules/packagea/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
When
For local path dependencies eg file:../packageA which are more than one level deep. Ie a local package references a local package which references a local package.
Where
- n/a
How
- n/a
Current Behavior
Fails to install nested dependency.
Steps to Reproduce
Reproducible in the following repo:
https://github.com/yahgwai/npm-ci-local-path
Run the following commands to reproduce:
- (cd packageC && npm i) // good - creates a package-lock.json
- (cd packageC && npm ci) // error - ENOENT
Expected Behavior
Should not error during npm ci
Who
- n/a
References
- n/a
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Bugthing that needs fixingthing that needs fixing