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] npm install --prefix="$PWD" adds invalid dependency to package.json #6960
Labels
Bug
thing that needs fixing
Priority 2
secondary priority issue
Release 9.x
work is associated with a specific npm 9 release
Comments
mehulkar
added
Bug
thing that needs fixing
Needs Triage
needs review for next steps
Release 9.x
work is associated with a specific npm 9 release
labels
Nov 3, 2023
Just curious; why are you using |
That's a great question and I don't know. It was in a CI script we had that was previously only running on macOS/Linux and I'm working on making it run on Windows. I'm planning to stop using it |
wraithgar
added
Priority 2
secondary priority issue
and removed
Needs Triage
needs review for next steps
labels
Nov 7, 2023
ficocelliguy
added a commit
to ficocelliguy/cli
that referenced
this issue
Feb 7, 2024
#7208 filed to resolve this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Bug
thing that needs fixing
Priority 2
secondary priority issue
Release 9.x
work is associated with a specific npm 9 release
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
On macOS, this does the expected thing (generates a
package-lock.json
:On Windows, however, it does strange things. It:
{ "dependencies": { "project": "file:" }}
topackage.json
project
pointing to PWDExpected Behavior
I expect Windows to have the same behavior. Particularly,
package.json
should not be modified.Steps To Reproduce
See above
Environment
The text was updated successfully, but these errors were encountered: