-
Notifications
You must be signed in to change notification settings - Fork 15
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
Update peer dependencies to include @typescript-eslint/parser
v6
#13
Comments
Hello, @hluisson , please :) 🔝 |
Here's the warning that appears (with $ pnpm install
WARN Issues with peer dependencies found
.
└─┬ eslint-plugin-jsx-expressions 1.3.1
└── ✕ unmet peer @typescript-eslint/parser@"^4.0.0 || ^5.0.0": found 6.2.1
|
And this actually causes a failure with $ npm i
npm notice
npm notice New major version of npm available! 8.19.2 -> 10.0.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.0.0
npm notice Run npm install -g [email protected] to update!
npm notice
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: @typescript-eslint/[email protected]
npm ERR! node_modules/@typescript-eslint/parser
npm ERR! peer @typescript-eslint/parser@"^6.3.0" from [email protected]
npm ERR! node_modules/eslint-config-upleveled
npm ERR! dev eslint-config-upleveled@"^5.0.4" from the root project
npm ERR! peer @typescript-eslint/parser@"^6.0.0 || ^6.0.0-alpha" from @typescript-eslint/[email protected]
npm ERR! node_modules/@typescript-eslint/eslint-plugin
npm ERR! peer @typescript-eslint/eslint-plugin@"^6.3.0" from [email protected]
npm ERR! node_modules/eslint-config-upleveled
npm ERR! dev eslint-config-upleveled@"^5.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @typescript-eslint/parser@"^4.0.0 || ^5.0.0" from [email protected]
npm ERR! node_modules/eslint-plugin-jsx-expressions
npm ERR! peer eslint-plugin-jsx-expressions@"^1.3.1" from [email protected]
npm ERR! node_modules/eslint-config-upleveled
npm ERR! dev eslint-config-upleveled@"^5.0.4" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: @typescript-eslint/[email protected]
npm ERR! node_modules/@typescript-eslint/parser
npm ERR! peer @typescript-eslint/parser@"^4.0.0 || ^5.0.0" from [email protected]
npm ERR! node_modules/eslint-plugin-jsx-expressions
npm ERR! peer eslint-plugin-jsx-expressions@"^1.3.1" from [email protected]
npm ERR! node_modules/eslint-config-upleveled
npm ERR! dev eslint-config-upleveled@"^5.0.4" 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! See /home/runner/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/runner/.npm/_logs/2023-09-05T11_35_09_217Z-debug-0.log |
@hluisson would you be open to upgrading the peer dependency on It may also need a switch away from the eslint-plugin-jsx-expressions/package.json Lines 26 to 29 in cb612d1
|
Hey - this is on my radar, but for fastest resolution feel free to submit a PR! |
I'm currently looking into it and noticed the following:
Another thing I noticed was that a change to the |
I recently tackled upgrading this with what seems like mostly similar issues here: You can look at that for inspiration, otherwise I might get around to making a similar PR here as well soon! |
WorkaroundUntil this is fixed, you can override the dependencies to the latest version: Eg using npm Overrides:
{
"overrides": {
"@typescript-eslint/eslint-plugin": "6.9.1",
"@typescript-eslint/parser": "6.9.1"
}
} (or Yarn Resolutions or pnpm Overrides) |
Hey all - thanks for your patience. I will publish 1.3.2 as soon as possible. |
1.3.2 is now live! |
@hluisson Thanks so much, I can confirm this is working now, no more peer dependency warnings 🙌 |
Typescript-eslint just released v6. I'm getting a peer dependency mismatch warning after updating.
The text was updated successfully, but these errors were encountered: