Support for nodejs16.x runtime

[ofhouse]

ToDo:

• Upgrade sammy: Add support for nodejs16.x runtime sammy#13
• Upgrade @vercel/build-utils
• Set default runtime to nodejs16.x in variables.tf
• (blocked) Wait for Terraform AWS Provider v4.15.0 to be released (Feature Request: nodejs16.x support for aws_lambda_function hashicorp/terraform-provider-aws#24714, build(deps): bump github.com/aws/aws-sdk-go from 1.44.10 to 1.44.13 hashicorp/terraform-provider-aws#24768)

[larahroth]

Hi! :D We are using your lovely library and noticed that edge functions now support node 16.

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.

Are we able to look into supporting node 16? Node 14 is significantly out of date at this point, especially with the version of npm it ships with. Let me know if you need help with anything on this, happy to help.

Thank you in advance! @ofhouse :D

[ofhouse]

Hey @nyt-larahelenaroth,

didn't noticed yet that Node.js 16 runtime was released to Lambda@Edge as well. Thanks for the reminder.

Upgrading should only have a small impact since it is only used by the router module.
The Next.js functions itself run on standard Lambdas that already support Node.js 16.

[larahroth]

@ofhouse Amazing! Thank you so much for replying & so glad to hear :D Please let us know timing so we can adjust once the support is deployed. Exciting news!