-
-
Notifications
You must be signed in to change notification settings - Fork 62
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 peerDependency warning when used with eslint-plugin-i #243
Conversation
Fixes the following warning e.g. in Yarn: ➤ YN0002: │ my-project@workspace:. doesn't provide eslint-plugin-import (p2dacd), requested by eslint-import-resolver-typescript The downside is that in order to support "either or", we need to make both eslint-plugin-import and eslint-plugin-i optional peerDependencies.
|
|
@wojtekmaj Marking a |
@wojtekmaj Sorry I didn't notice this PR for a long time, let's continue discussion at #248 (comment) |
I don't understand, as per https://docs.npmjs.com/cli/v10/configuring-npm/package-json#peerdependenciesmeta I believe |
Ah yes, this may be Yarn specific. Stupid NPM and their stupid peerDependencies auto install :/ |
Why can't we merge this for npm users? Making it optional should allow new users to avoid installing |
@kurtextrem |
Fixes the following warning e.g. in Yarn:
The downside is that in order to support "either or", we need to make both eslint-plugin-import and eslint-plugin-i optional peerDependencies.