You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 10, 2021. It is now read-only.
npm ci --production fails with enoent ENOENT: no such file or directory error.
When
When a prod dependency A and a dev dependency B both depend on a dependency C that is not installed through a registry (eg. was installed through github), and running in production-only mode, the updateJson process fails because the parent dependency package.json file cannot be resolved.
Where
Module requesting private github repo dependency.
How
Current Behavior
fails with enoent ENOENT: no such file or directory error.
What / Why
npm ci --production
fails withenoent ENOENT: no such file or directory
error.When
When a prod dependency A and a dev dependency B both depend on a dependency C that is not installed through a registry (eg. was installed through github), and running in production-only mode, the
updateJson
process fails because the parent dependencypackage.json
file cannot be resolved.Where
Module requesting private github repo dependency.
How
Current Behavior
enoent ENOENT: no such file or directory
error.Steps to Reproduce
See repro test on #18
Expected Behavior
The text was updated successfully, but these errors were encountered: