-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Closed
Labels
Bugthing that needs fixingthing that needs fixingNeeds Triageneeds review for next stepsneeds review for next stepsRelease 10.xRelease 7.xwork is associated with a specific npm 7 releasework is associated with a specific npm 7 releaseRelease 8.xwork is associated with a specific npm 8 releasework is associated with a specific npm 8 releaseRelease 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
Clone https://github.com/ljharb/list-exports
run npm install.
see it fail.
Expected Behavior
It doesn't fail.
Steps To Reproduce
See above.
Environment
- npm: v7 - v10.10
- Node.js: irrelevant, but i was using v20.5.1
- OS Name: Mac OS
- System Model Name: Macbook Pro
- npm config: not relevant, the only local config i have is
package-lock=falsein the npmrc file.
Metadata
Metadata
Assignees
Labels
Bugthing that needs fixingthing that needs fixingNeeds Triageneeds review for next stepsneeds review for next stepsRelease 10.xRelease 7.xwork is associated with a specific npm 7 releasework is associated with a specific npm 7 releaseRelease 8.xwork is associated with a specific npm 8 releasework is associated with a specific npm 8 releaseRelease 9.xwork is associated with a specific npm 9 releasework is associated with a specific npm 9 release