-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Open
Labels
Bugthing that needs fixingthing that needs fixingNeeds Triageneeds review for next stepsneeds review for next steps
Description
Is there an existing issue for this?
- I have searched the existing issues
This issue exists in the latest npm version
- I am using the latest npm
Current Behavior
I need to do npm install twice to have the correct package-lock.json
Expected Behavior
package-lock.json is good on first npm install
Steps To Reproduce
- Download repro repo: https://github.com/Saibamen/npm-bug-repro-workspaces
npm run clean:all(delete allnode_modulesfolders + lock files)npm installnpm audit --omit=dev- ❌ See vulnerabilities from lodash package
npm run clean(deletenode_modulesand lock file, but only in root folder)npm installnpm audit --omit=dev- ❎ No vulnerabilities and changed lock file
Environment
- OS: Windows 11
; node bin location = C:\nvm4w\nodejs\node.exe
; node version = v24.14.0
; npm local prefix = C:\DEV\test_npm
; npm version = 11.12.0
; cwd = C:\DEV\test_npm
; HOME = C:\Users\AdamStachowiczReactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Bugthing that needs fixingthing that needs fixingNeeds Triageneeds review for next stepsneeds review for next steps