-
Notifications
You must be signed in to change notification settings - Fork 10
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
feature/issue 1328 customize Vercel adapter serverless runtime nodejs version #1330
feature/issue 1328 customize Vercel adapter serverless runtime nodejs version #1330
Conversation
c05a040
to
67c4635
Compare
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.
Looks like we were able to stay on Node 18 in #1326 , so we should reset the default version back to nodejs18.x
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.
Based on #1372 / #1373 it looks like we can keep the minimum version for Greenwood as 18.x
, but not sure if that's useful to what people are using? Given where NodeJS is in the LTS cycle, perhaps 20.x
makes sense, right in the middle?
Mostly just thinking of this from what makes a good default value for this plugin? Or just always keep it aligned with Greenwood's minimum version for consistency? 🤔
67c4635
to
8b39287
Compare
Related Issue
resolves #1329
Documentation
N / A
Summary of Changes
nodejs20.x
TODO
20.x
(latest LTS) #1202 / enhancement/issue 1317 import map generation refactor for exports and leveragingimport.meta.resolve
#132620.x
for now, actually - feature/issue 1328 customize Vercel adapter serverless runtime nodejs version #1330 (review)