Skip to content
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

Support for Node v16 #315

Closed
anudit opened this issue May 16, 2022 · 4 comments
Closed

Support for Node v16 #315

anudit opened this issue May 16, 2022 · 4 comments
Labels
question Question about usage of the library
Milestone

Comments

@anudit
Copy link

anudit commented May 16, 2022

Could we upgrade @vercel/build-utils to 2.17.0 from 2.12.1 to support the new Node 16 runtime?

Running into the following error currently,
image

@ofhouse
Copy link
Member

ofhouse commented May 16, 2022

Hi, yes Node 16 runtime support is on the radar, but takes a few extra steps besides just upgrading the @vercel/build-utils dependecy:

Support for the Lambda runtime nodejs16.x is tracked here: #316

@ofhouse
Copy link
Member

ofhouse commented May 16, 2022

Oh, misinterpreted your issue.
You are asking for Node.js 16 support for the CLI not the nodejs16.x runtime 🙈

@ofhouse
Copy link
Member

ofhouse commented May 16, 2022

However I think setting the "engines": { "node": "14.x" } field in your package.json is the right solution here.
The CLI should still build fine with Node.js 16, but since we currently don't support the nodejs16.x runtime, it does not make sense to allow the creation of Lambdas with Node.js 16 as target.

@ofhouse ofhouse added the question Question about usage of the library label May 16, 2022
@ofhouse ofhouse added this to the v0.13.0 milestone May 26, 2022
@ofhouse ofhouse closed this as completed May 28, 2022
@ofhouse
Copy link
Member

ofhouse commented May 28, 2022

This has been fixed in v0.13.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Question about usage of the library
Projects
None yet
Development

No branches or pull requests

2 participants