-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
"dependencies": {
"eslint": "^8.57.1",
"@stylistic/eslint-plugin": ">=3.1.0"
}
Same issue also when the ^ is removed
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: global-shadow@undefined
npm error Found: eslint@8.57.1
npm error node_modules/eslint
npm error eslint@"^8.57.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@">=9.0.0" from @stylistic/eslint-plugin@5.7.0
npm error node_modules/@stylistic/eslint-plugin
npm error @stylistic/eslint-plugin@">=3.1.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
Expected Behavior
@stylistic/eslint-plugin 3.1.0 is compatible with eslint 8.57.1 and set as peer dependency by it. Why is it unable to resolve this basic case?
Steps To Reproduce
- put these dependencies in package.json, no other dependencies
- npm install --package-lock-only
Environment
- npm: 11.7.0
- Node.js: v20.19.6
- npm config:
; "global" config from /usr/etc/npmrc
prefix = "/usr"
update-notifier = false
; node bin location = /usr/bin/node
; node version = v20.19.6
; npm local prefix = /my/path/temp
; npm version = 11.7.0
; cwd = /my/path/temp
; HOME = /home/foo
; Run `npm config ls -l` to show all defaults.