-
Notifications
You must be signed in to change notification settings - Fork 4
Switch to ESM #572
Comments
ESM support is now available on AWS Lambda: https://aws.amazon.com/de/blogs/compute/using-node-js-es-modules-and-top-level-await-in-aws-lambda/ See NordicSemiconductor/asset-tracker-cloud-aws-js#572
* feat: switch to ESM and esbuild ESM support is now available on AWS Lambda: https://aws.amazon.com/de/blogs/compute/using-node-js-es-modules-and-top-level-await-in-aws-lambda/ See NordicSemiconductor/asset-tracker-cloud-aws-js#572 Closes #365
* feat: switch to ESM and esbuild ESM support is now available on AWS Lambda: https://aws.amazon.com/de/blogs/compute/using-node-js-es-modules-and-top-level-await-in-aws-lambda/ See NordicSemiconductor/asset-tracker-cloud-aws-js#572 Closes #365 BREAKING CHANGE: this requires lambdas to be authored for ESM
🎉 This issue has been resolved in version 32.6.0-switch-to-esm.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 33.0.0-switch-to-esm.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 33.1.0-switch-to-esm.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Blocked by ESM lambda not working with layers. |
Hi Markus, I guess you are also still stuck with this? I created an issue here: aws/aws-cdk#23333 |
A few days ago I started a new CDK TypeScript project and think we are now good to move to ESM: see #1185. I have not observed the problem that you describe in your issue with having to maintain multiple tsconfig files. |
Great! I will take a look |
- use [new protocol definitions from docs](NordicSemiconductor/asset-tracker-cloud-docs#665) - switch to ES modules (Closes #572) - get rid of fp-ts (makes code too complicated, no clear benefit)
🎉 This issue has been resolved in version 40.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
AWS Lambda does not support ESM, yet. So this is on hold until it's implemented on AWS side.ESM support in Node.js v14 is here: https://aws.amazon.com/de/blogs/compute/using-node-js-es-modules-and-top-level-await-in-aws-lambda/
node-fetch v3
The text was updated successfully, but these errors were encountered: