-
-
Notifications
You must be signed in to change notification settings - Fork 564
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
Support eslint-plugin-n 17 #412
Comments
Similar issue with eslint@9 upgrade npm ERR! While resolving: @repository
npm ERR! Found: [email protected]
npm ERR! node_modules/eslint
npm ERR! dev eslint@"^9.1.1" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^8.0.1" from [email protected]
npm ERR! node_modules/eslint-config-standard
npm ERR! dev eslint-config-standard@"^17.1.0" 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. |
We have the same issue upgrading But it seems since month only the renovate bot is committing on this repo. |
There is a renovate update PR waiting |
Would love this too please |
It just a robot. |
It looks like 16 is EOL according to https://www.npmjs.com/package/eslint-plugin-n |
would appreciate if some of the maintainers would take some time for this, thank you! |
@jeromy-cannon I'm spending my time over at https://github.com/neostandard/neostandard now – it works great with latest eslint-plugin-n and I won't personally do any work on standard here until we hopefully reconcile the projects at a future date |
thank you for dropping a line. I'll check out neostandard and see how it fits in my project, thanks for the recommendation and explanation! |
Here's what I did
I have a project that declares both
eslint-config-standard
andeslint-plugin-n
as dev dependencies. Periodically, I upgrade all dependencies to latest versions I can. Today's attempt produced this:What I expected to happen
npm install
works and all the linting stuff still works.What seems to have happened
eslint-config-standard
does not supporteslint-plugin-n
version 17:The text was updated successfully, but these errors were encountered: