You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
One possible issue that we have encountered while using the aws-otel-nodejs lambda layer is the incompatibility with Middy, a middleware engine for lambda handlers. Middy has recently dropped support for CommonJs, which means we cannot use module.exports as required by the aws-otel documentation.
Describe the solution you'd like
Support for ES6 modules (imports/exports) to enable ESModules rather than CommonJS so we can use the import and export syntax in your Node.js applications, instead of exporting modules.
This issue is stale because it has been open 90 days with no activity. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled
Is your feature request related to a problem? Please describe.
One possible issue that we have encountered while using the
aws-otel-nodejs
lambda layer is the incompatibility with Middy, a middleware engine for lambda handlers. Middy has recently dropped support for CommonJs, which means we cannot usemodule.exports
as required by the aws-otel documentation.Describe the solution you'd like
Support for ES6 modules (imports/exports) to enable ESModules rather than CommonJS so we can use the import and export syntax in your Node.js applications, instead of exporting modules.
Describe alternatives you've considered
Another option we have is to follow the open telemetry example for JavaScript serverless functions and write our own code to integrate it, instead of relying on the lambda layer.
Additional context
ESM is recognized as the official standard by NodeJs' docs.
The text was updated successfully, but these errors were encountered: