-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
NPM 7 installs very old version #2000
Comments
What is eslint-config-import? |
I would suggest not using that package, as it hasn’t been maintained in 5 years, i don’t have publish rights on it, and i can’t find any record of that package.json file in this repo. |
Additionally, its peer dep on 0.13 of this plugin means that you are forced to use 0.13 of the plugin with it, otherwise your dep graph is invalid. |
OK thanks. Is an old project, will remove |
For posterity, here’s https://github.com/benmosher/eslint-plugin-import/tree/v0.13.0/config, and it was removed in 369c9dd#diff-b79606fb3afea5bd1609ed40b622142f1c98125abcfe89a76a661b0e8e343910 before this plugin reached v1. |
This might be related to the #1986 issue so if it is apologies for the noise.
Running
npm i --save-dev eslint-plugin-import eslint-config-import
in an empty project brings in a super old version of the plugin that seems pinned to theeslint-config-import
version (0.13.0). In turn this is causing me problems when usingeslint-import-resolver-alias
which expectseslint-plugin-import@">=1.4.0
But all is fine if I force the npm install.
The text was updated successfully, but these errors were encountered: