-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Bump node version to 16.13.0 #5934
Conversation
Just curious: was there a reason for choosing v16.13 specifically, rather than v16? |
Could you update the README as well? It references version 14 in the setup instructions |
Hey @Gudahtt, I just now realized you left some comments,
I think
Yes |
Done @Gudahtt |
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.
LGTM!
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.
nice ^ we officially make the switch to .node-version
and set v16 in 0.70
but our 0.66.5 .nvmrc
ahead on 16's perfectly fine
but after SES/lockdown likely needs work LavaMoat-side to sandbox compile/run time
since we've been on v14 only couple months - i'll check w the team to plan/start early
i also bumped to v18 fb picked for 0.71+ (but got few months till Node 16 EOL: 2023-09-11)
our 0.71.4 branch (i'm using for lockdown) is behind on v16.14.0 so also checking this is ok
Node 19's been around few months too (got unofficially working for RN)
so hopefully can bundle the LavaMoat work to support 16/18/19 at same time
No description provided.