feat(lambda-nodejs): Expose optional props for advanced usage of esbuild

[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

Like in my current use case I need to use tsconfig with the name tsconfig.release.json and I find out that the current implementation of esbuild is not allowing me to use so I ended up renaming my tsconfig just this.

once esbuild generates the bundled the there is no way to identify for users to view those bundled if required.

also good to have a meta file for the build to view stats of the bundler many tools support JSON meta-file i.e bundle buddy

Proposed Solution

// If the file is on root directory
const props: NodejsFunctionProps = {
             entry: `index.ts`,
             bundling: {
                 minify: false,
                 sourceMap: true,
                 metaFile: true,
                 tsConfig: 'tsconfig.release.json'
             },
         }

Other

// If the file is not on root directory and src folder
const props: NodejsFunctionProps = {
             entry: `index.ts`,
             bundling: {
                 minify: false,
                 sourceMap: true,
                 metaFile: true,
                 tsConfig: 'src/tsconfig.release.json'
             },
         }

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

---

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.