-
-
Notifications
You must be signed in to change notification settings - Fork 3
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: Don't require ESLint #25
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Marking ESLint as optional is a good idea. LGTM
I think that to allow installing ESLint v8.x without the Line 71 in 08fd5d3
Making the peer dependency optional will allow a package to install For the same reason in
Probably most users of this plugin will already have a new version |
Hmm, not what we want. I wonder if it's best just remove the peer dependency altogether? |
Makes sense I think, if it should be possible to install this package irrespective of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
Prerequisites checklist
What is the purpose of this pull request?
Make ESLint an optional peer dependency.
What changes did you make? (Give an overview)
Added
peerDependenciesMeta
topackage.json
in order to seteslint
as an optional peer dependency.Practically speaking, the plugin doesn't require ESLint to be useful. We are using it in the Code Explorer without ESLint, where it's installation is causing npm errors because Code Explorer uses ESLint v8.x.
Related Issues
Is there anything you'd like reviewers to focus on?
It seems like we shouldn't block installation of this package even if ESLint isn't installed or ESLint v8.x is installed, but let me know if anyone has a different opinion. From what I can tell, this change won't have any noticeable effect to most users of this plugin.