(aws-lambda-nodejs): Expose AssetStaging.exclude as prop to ignore node_modules from fingerprinting

[relm923]

Describe the feature

Add bundling.exclude property to NodejsFunction that is passed to the Asset here

This would allow certain paths from being included in the fingerprint/assetHash giving developers more control without having to fully customize the hashing logic

Use Case

When using the NodejsFunction.nodeModules property the listed modules (and their dependencies) are included directly in the bundled asset. This leads to the containing node_modules directory to directly influence the calculated assetHash. The contents of node_modules can be unstable for a large number of reasons leading to unnecessary deployments

Proposed Solution

No response

Other Information

No response

Acknowledgements

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

CDK version used

2.181.1

Environment details (OS name and version, etc.)

N/A

[pahud]

Thank you. While this makes sense to me, we still need more inputs from the maintainers. I am bringing it up to the team for further inputs.

[relm923]

This is particularly problematic due to

aws-cdk/packages/aws-cdk-lib/aws-lambda-nodejs/lib/package-manager.ts

Line 46 in b532c1b

// --no-prefer-frozen-lockfile (works the same as yarn's --no-immutable) Disable --frozen-lockfile that is enabled by default in CI environments (https://github.com/pnpm/pnpm/issues/1994).

causing pnpm-lock.yaml and node_modules to change on every synth