Update to Node 20 #1317
Update to Node 20 #1317
Conversation
🦋 Changeset detectedLatest commit: 86503f5 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
| - `@types/node` package version | ||
| - CI/CD configuration (`.buildkite/pipeline.yml`, `Dockerfile`, etc.) | ||
|
|
||
| If you are updating your AWS Lambda runtime to `nodejs20.x`, consider reading the [release announcement](https://aws.amazon.com/blogs/compute/node-js-20-x-runtime-now-available-in-aws-lambda/) as there are some breaking changes with this upgrade. |
There was a problem hiding this comment.
For optimal performance, and to have full control over your code dependencies, we recommend bundling and minifying the AWS SDK in your deployment package, rather than using the SDK included in the runtime. For more information, see Optimizing Node.js dependencies in AWS Lambda.
hmmm
.changeset/spotty-nails-jam.md
Outdated
| "skuba": patch | ||
| --- | ||
|
|
||
| template/*: Update to Node 20 |
There was a problem hiding this comment.
| template/*: Update to Node 20 | |
| template: Update to Node 20 |
| @@ -1 +1 @@ | |||
| 18 | |||
There was a problem hiding this comment.
I've left the package.json engines alone in the packages as that would force consumers to update to node 20 which doesn't quite seem right?
Upgrade to Node 20
Resolves #1297