forked from mysticatea/eslint-utils
-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Drop older node versions from engines.node
(align with ESLint 9?)
#232
Labels
Comments
This was referenced Sep 17, 2024
I am completely in favour of aligning with eslint's supported version ranges 👍 We have already made the change in |
🎉 This issue has been resolved in version 5.0.0-alpha.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Closed by #242 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To keep up to date with our dependencies (#231, #228, #226, #222, #199) and to enable us to use modern JS features (#204 (comment)) I would suggest that we align with ESLint 9's engine range, ^18.18.0 || ^20.9.0 || >=21.1.0, for the next major release.
As I mention in #204 (comment), but haven't gotten any feedback on, I would like to address this issue before spending time on undoing modern JS to something old only to have us drop the old engines right afterwards.
The text was updated successfully, but these errors were encountered: