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] file:
dependency is locked without package name when install is run for the 1st time
#6430
Comments
Can someone, please, look into this lock file instability issue? |
Hi all, this issue is still present, can someone please confirm/reproduce it and fix it? Thank you in advance! |
I am also experiencing this issue and have looked into it a bit. The issue is only present when the folder name of the I have created a reproduction test for this issue in this branch: https://github.com/sonallux/npm/tree/chore/6430-add-reproduction-test-case and opened PR #7228 |
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
Please run the repro steps below. Currently when a
file:
dependency is required, it is added to the lock file without a name when the npm install is run for the 1st time. Even if there is no dependency change, when the npm install is rerun, the lock file is changed.Expected Behavior
no lock file change
Steps To Reproduce
git clone https://github.com/atk4/ui.git
cd js
rm package-lock.json
npm i --package-lock-only
cp package-lock.json package-lock2.json
npm i --package-lock-only
packages
->.eslint
->name
key is added to the lock file (diff package-lock2.json package-lock.json
)Environment
The text was updated successfully, but these errors were encountered: