-
Notifications
You must be signed in to change notification settings - Fork 181
[Major] update node.js to v20 #995
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
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 268e2b9 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
aada65a to
268e2b9
Compare
commit: |
conico974
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.
For upgrading to Node 20, we also need to upgrade the actual AWS CI deployment, which still use Node 18.
And it probably means that we need to drop support for at least Next 12, and very likely 13 as well
Yeah, that makes sense. Given that Next.js v14 has been out for a while (2023) I think that dropping support for older Next versions is reasonable. wdyt? |
|
I think supporting |
|
Chiming in here, AWS have just released node 24 support. In terms of supporting next.js versions, Vercel themselves only support 15 and 16 (latest two versions) at the time of writing. https://nextjs.org/support-policy In AWS terms, node 20 will be deprecated from April '26 - https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html |
Updates minimum required Node.js version to v20