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
feat: update default nodejs version to 16 #1138
Conversation
β± Benchmark resultsComparing with 20fe86c largeDepsEsbuild: 5.7sβ¬οΈ 2.05% decrease vs. 20fe86c
largeDepsZisi: 43.1s
|
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 guess we need to coordinate this release with bitballon exactly?
π€ I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use -- conventional-commit-lint bot |
If I am not wrong, this project prepares the functions to be uploaded as a zip. So, it could have been even merged before as we are just changing the default runtime. But let's do it after the default has been rolled out 100% so we know is not causing any problem, and then we merge the rest. |
BTW @danez, I saw the bot reported like a 50% decreased . I guess that good, but not sure if is it related to the nodejs version or just some random numbers that depends on the time it was executed π€ |
I just did another commit and results are totally different, so already answered π |
t.is(getNodeVersion('nodejs12.x'), 12) | ||
t.is(getNodeVersion('nodejs8.x'), 8) | ||
t.is(getNodeVersion('12.x'), 12) | ||
t.is(getNodeVersion('8.x'), 8) | ||
t.is(getNodeVersion('node14'), DEFAULT_NODE_VERSION) | ||
t.is(getNodeVersion('node16'), DEFAULT_NODE_VERSION) |
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 know you jsut changed the number, but it was actually wrong before. node1X
is not a valid specifier. It needs to be either nodejs16.x
or 16.x
. It works though because in case the input cannot be parse it defaults to the default nodejs version. Hence the next line in this file with :shrug:
t.is(getNodeVersion('node16'), DEFAULT_NODE_VERSION) | |
t.is(getNodeVersion('16.x'), DEFAULT_NODE_VERSION) |
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 think this unit test check that something like "nodeVersion"
is invalid so it uses the default one. Not sure if we should change it
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.
Okay I see.
Just too clarify again, this has nothing todo with the runtime, but with the output target of our bundlers. So with the runtime now being default nodejs 16 in bitballon, but we still bundle the functions here for node14 (which is fine and works, but can be better optimized if we also set it to node16). This PR changes that. |
π Thanks for submitting a pull request! π
Summary
As commented by @Skn0tt, we are updating the default nodejs runtime to version 16 but was missing here. The version will be updated on Monday, so we can release it after that. Let me know if I am doing something wrong as it is my first PR here π
For us to review and ship your PR efficiently, please perform the following steps:
This ensures we can discuss the changes and get feedback from everyone that should be involved. If you`re fixing
a typo or something that`s on fire π₯ (e.g. incident related), you can skip this step.
passes our tests.
A picture of a cute animal (not mandatory, but encouraged)