-
Notifications
You must be signed in to change notification settings - Fork 44
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
Upgrade Nodejs to 22 #2619
base: main
Are you sure you want to change the base?
Upgrade Nodejs to 22 #2619
Conversation
The latest updates on your projects. Learn more about Vercel for Git βοΈ
|
@@ -330,6 +330,6 @@ | |||
"dist" | |||
], | |||
"engines": { | |||
"node": "16.* || >= 18" | |||
"node": ">= 18" |
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.
@alex-ju I'm curious your opinion on this. Technically this should be considered a breaking change, but AFAICT we don't have any known consumers using Node 16. On the other hand, there is no real need for us to make this change either.
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.
According to the latest findings around the API our consumers are mostly concerned about the changes not affecting them, rather than following a rigid versioning policy. Based on this, and considering Ember dropped support for Node 16 in v5.11.0, so I'd say we can do it in a minor release too.
π Summary
16* || >= 18
to>=18
20.x
to the latest LTS of22.x
π οΈ Detailed description
Removing support for Node.js 16 due to the following factors
>18
>=18.12.0
π External links
Jira ticket: HDS-4265
π Component checklist
π¬ Please consider using conventional comments when reviewing this PR.