(aws-lambda-nodejs): Expose optional settings of logging and preserve name of function and classes while bundling

[hassanazharkhan]

This feature request is to add bundling props while bundling from local or docker build from esbuild, there are lots of features that needs to be exposed from aws-lambda-nodejs

Use Case

There are cases where bundler prints warnings and errors in the terminal but most of the time these warnings are just warning and ignorable, so with the current implementation of bundler props we don't have any exposed settings to change the log level of the bundler.

Along with the above, there are no options to preserve the name of function and classes while bundling this is really useful where the name function or class used somewhere in the code dynamically.

I am also thinking to add a property that will be used to identify tsconfig if one doesn't want to use default tsconfig that property will tell the esbuild to use a particular config, i.e bundler.tsconfig.json. there are valid use cases of this.

Proposed Solution

const props: NodejsFunctionProps = {
             entry: `index.ts`,
             bundling: {
                 minify: false,
                 sourceMap: true,
                 logLevel: LogLevel.ERROR,
                 keepNames: true
             },
         }

Other

• 👋 I can implement this feature request, it won't be difficult

---

This is a 🚀 Feature Request

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[hassanazharkhan]

@jogold When this will be available?

[jogold]

@jogold When this will be available?

In the next release