- Notifications
You must be signed in to change notification settings - Fork115
Support for Node v22#359
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Conversation
Features- Update warmer to node 22- Add support to nodejs v22
PL-403 PL-475
PL-403 PL-475
This reverts commitf2f5407.
contexD commentedAug 26, 2025
closes#361 |
nelsonlazar commentedNov 16, 2025
Hi@juanjoDiaz@sebekz |
thiagosanches commentedNov 24, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Node 24 is now available on AWS Lambda runtimes! https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html |
thiagosanches commentedNov 24, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Humm... Maybe it's better to have the runtime parametrized? So, there will be no runtime version hard-coded on the plugin, and we can use For backward compatibility, the plugin can always default to a version, but it would be good to have an option so developers can overwrite to newer versions when available. |
Upgrading from Node.js 20 to Node.js 22 for the following reasons: