-
Couldn't load subscription status.
- Fork 1.2k
Update node support to 18 #1117
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
I noticed the supported Node version is also mentioned in the AWS deployment guide. I can submit a separate PR if you would like.
Looking at the Guide it also shows how to install node 14 so we would need to explain you can install any of the versions I suppose. I think this would be better put in another PR if you don't mind :) |
OK for me. We are going to revise the guide in Q4 anyway. Thanks for the PR! |
|
Thanks, @alexandrebodin. |
|
Node 18 isn't LTS yet so we don't recommend it for now but will once it goes LTS and 14 goes in maintenance :D |
OK, thanks, but should we recommend 16 now (instead of 14) in the last sentence ("The |
|
Ha sorry yes node 16 should totally be recommended :D |
Node.js 18.12.0 reached LTS status a couple days ago, so will it become the recommended version now? |
I'll check with the engineering team :) |

What does it do?
Add node 18 support info in the doc
Why is it needed?
We added support for node 18 in the codebase and will be released with the upcoming 4.3.9
Related issue(s)/PR(s)
Let us know if this is related to any issue/pull request