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
Chore: remove dead code from prefer-const #8683
Conversation
This code was added to work around a bug in acorn (acornjs/acorn#487), which has since been fixed.
@not-an-aardvark, thanks for your PR! By analyzing the history of the files in this pull request, we identified @mysticatea, @NickHeiner and @vitorbal to be potential reviewers. |
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.
This change LGTM, but I want to make sure our dependency specifiers will definitely prevent this from recurring for our users.
- Does latest espree specify a version range for acorn where this is definitely fixed in all specified versions?
- Does the minimum version of espree allowed by ESLint's specified version range point to a version of espree that consumes acorn versions which definitely have this fixed?
If the answer to either of those questions is no or unsure, then I think we should potentially do one or both of the below:
- Upgrade the Acorn version specification in espree and cut a patch release
- Upgrade the espree version specification in ESLint as part of this PR
If you believe that the minimum supported espree points to a minimum supported acorn which has the Acorn bug fixed, ping me and I'll switch to approve.
@platinumazure We depend on |
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!
What is the purpose of this pull request? (put an "X" next to item)
[x] Other, please explain:
What changes did you make? (Give an overview)
This code was added to work around a bug in acorn (acornjs/acorn#487), which has since been fixed.
Is there anything you'd like reviewers to focus on?
Nothing in particular