-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
[BUG] git dependency installed with npm ci triggers error with npm prune --production #514
Comments
This was a breaking change for our builds when we bumped node:10.16 to node:10.17 (since that bumps npm 6.9.0 to 6.11.3) |
Is there any update or resolution to this issue? With the recent security advisory to update to 6.13.4, this issue is preventing us from ensuring our team and their systems are safe. |
Looks like a duplicate of #624. |
Seems like it, yes. This was created before #624 but that issue has more discussion. I'll go ahead and close this issue and leave the discussion there. |
Fix: npm/cli#624 Fix: npm/cli#642 Fix: npm/cli#514 Infer the ownership of a git command invocation based on the cwd, if one is specified.
When installing some git dependencies using the Docker image node:10-alpine via
npm ci
, attempts tonpm prune --production
result in an error like:To help replicate the issue, I have a directory that contains a
package.json
andpackage-lock.json
. I then have aDockerfile
which when building, illustrates the issue.I've created a repository at https://github.com/Cherry/npm-prune-ci-bug detailing this, including commands to run to replicate the issue.
Last known working version:
6.10.3
. This issue does not occur if I use npm version6.10.3
or earlier.Tested versions that throw the above error:
It appears this regression was introduced in
6.11.0
, and exists through to the latest version.If I can provide any further information, please let me know.
The text was updated successfully, but these errors were encountered: