-
-
Notifications
You must be signed in to change notification settings - Fork 220
feat!: Require Node.js ^20.19.0 || ^22.13.0 || >=24
#696
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
Conversation
fasttime
left a comment
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! Waiting for another review.
|
there is a conflict now. |
0b5fb12 to
31b5cf2
Compare
Resolved now. |
SwetaTanwar
left a comment
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.
Changes LGTM!
|
@mdjermanovic does this change mean that espree 10 (and thus, eslint 9) can't ever support ecmaVersion 2025, which includes import assertions? |
|
espree 10 and eslint 9 already fully support ecmaVersion 2025. |
|
Thanks; I clarified that in the discord. It turns out it's a different issue with eslint; i'll keep looking into it. |
Prerequisites checklist
What is the purpose of this pull request?
Aligns supported Node.js versions with ESLint v10.
What changes did you make? (Give an overview)
Updated
package.jsonof theespree,eslint-scope, andeslint-visitor-keyspackages to require:This drops support for Node.js 18.
Also updated CI configs and docs accordingly.
Related Issues
Refs eslint/eslint#19969
Is there anything you'd like reviewers to focus on?
Did I miss any places that should be updated?