Skip to content
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

Fix peer deps range #356

Merged
merged 1 commit into from
May 11, 2024
Merged

Fix peer deps range #356

merged 1 commit into from
May 11, 2024

Conversation

mizdra
Copy link
Owner

@mizdra mizdra commented May 11, 2024

There was an error in the notation of the version range for peerDeps. As a result, versions that should have been allowed were not allowed.

$ npm i -D eslint-interactive
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: undefined@undefined
npm ERR! Found: eslint@8.57.0
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"^8.57.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@">=8.45.0, 9.0.0-alpha.0" from eslint-interactive@11.0.1
npm ERR! node_modules/eslint-interactive
npm ERR!   dev eslint-interactive@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /Users/mizdra/.npm/_logs/2024-05-11T15_01_04_642Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /Users/mizdra/.npm/_logs/2024-05-11T15_01_04_642Z-debug-0.log

@mizdra mizdra added the Type: Bug Bug or Bug fixes label May 11, 2024
@mizdra mizdra merged commit c4f0f90 into main May 11, 2024
26 checks passed
@mizdra mizdra deleted the fix-peer-deps branch May 11, 2024 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Bug or Bug fixes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant