-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Closed
Labels
Bugthing that needs fixingthing that needs fixingPriority 1high priority issuehigh priority issueRelease 9.xwork is associated with a specific npm 9 releasework is associated with a specific npm 9 release
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
See the two commits in this repo.
The first commit is the result of running:
> npm install @pmmmwh/[email protected] [email protected]
added 135 packages in 6s
This command exits without error, and correctly installs to node_modules/ and package-lock.json. However, the resulting tree is invalid, according to npm ci:
❯ npm ci
npm ERR! code EUSAGE
npm ERR!
npm ERR! `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.
The second commit is the result of running npm install again. This updates the package lock to a valid tree, and npm ci now completes successfully.
Expected Behavior
It shouldn't be necessary to run npm install twice to get a valid tree.
Steps To Reproduce
See current behavior for a minimal repro repository.
Environment
- npm: 9.1.1
- Node.js: 18.12.0
- OS Name: macOS
- System Model Name: MacBook Pro (16-inch, 2019)
- npm config: none
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Bugthing that needs fixingthing that needs fixingPriority 1high priority issuehigh priority issueRelease 9.xwork is associated with a specific npm 9 releasework is associated with a specific npm 9 release