lambda-js: Add note about esbuild module exports

[indrora]

This change adds a short blurb about requirements for users who are using esbuild.

As discussed in aws-observability/aws-otel-lambda#99 there is a quirk of esbuild that causes exported functions using the export keyword to be marked immutable in the transpiled JS. As a result, you must use module.exports instead, which is passed along by the esbuild transpilation process unscathed.

[senock-dag]

Hi @indrora - good idea adding a note to the readme!

I'm running into the same issue, but the solution I see doesn't work with my implementation and I'm trying to troubleshoot what's going on.

If I update my exports to use module.exports, the other files that import my handler receives the following error:

Module '"../../../../src/authorizer"' declares 'authorizer' locally, but it is not exported

Do you have any advice on how I can use module.exports within my TS files?

[vasireddy99]

Hi @indrora - good idea adding a note to the readme!

I'm running into the same issue, but the solution I see doesn't work with my implementation and I'm trying to troubleshoot what's going on.

If I update my exports to use module.exports, the other files that import my handler receives the following error:

Module '"../../../../src/authorizer"' declares 'authorizer' locally, but it is not exported

Do you have any advice on how I can use module.exports within my TS files?

I do not have the total context on the suggestion but based on the context but you can try using like - module.exports = authorizer;