-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore: drop support for node v14.17, v17 #5971
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
BREAKING CHANGE: drops support for node v17
Thanks for the PR, @bmish! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
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.
💯, thanks!
Love to see those versions ticking up 😄
BREAKING CHANGE:
Drops support for end-of-life node v14.17 and v17
Fixes #5917.
As per: #5917 (comment)
Using minimum Node 14.18 enables full support for
node:
protocol imports: https://2ality.com/2021/12/node-protocol-imports.htmlNode 17 is end-of-life already.