(aws-lambda-nodejs): Support `bun` lockfiles for NodejsFunction bundling

[blimmer]

Describe the feature

Today, NodejsFunction supports lockfiles from the following ecosystems:

• NPM
• Yarn
• PNPM

bun is gaining in popularity and has its own lockfile, bun.lockb. It would be great if NodejsFunction supported using this lockfile.

Use Case

We've been migrating our apps to use bun since it's so much faster than node. However, when creating a new NodejsFunction with a bun lockfile, we get this error:

Error: Cannot find a package lock file (pnpm-lock.yaml, yarn.lock or package-lock.json). Please specify it with depsLockFilePath.

For now, we'll probably move over to a supported package manager, but we'd love to see native support for bun.lockb.

Proposed Solution

Update the bundling logic to include bun and support bun install-ing.

Other Information

No response

Acknowledgements

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

CDK version used

2.162.1

Environment details (OS name and version, etc.)

MacOS

[khushail]

Thanks @blimmer for submitting the feature request.

[blimmer]

Thanks @khushail - I've got a PR ready for review here: https://github.com/aws/aws-cdk/pull/31770

[epoctic]

I don't recommend developing using Bun and deploying to a Node platform. While I'm sure you'd be fine in the vast majority of cases, it could lead to some particularly annoying bugs.

Maybe I'm missing something, but it seems like this could only lead to confusion if users expect lock file support to imply Bun engine use.

Edit: After thinking on it a bit more, I think you'd likely be okay. The issues I've seen were related to moving Node projects to Bun, rather than the other way around.

[blimmer]

This logic just allows installing dependencies from package.json when you have a bun lockfile. Since bun uses the standard node_modules resolution of packages, I think we'd be OK in the vast majority of cases.

[blimmer]

Something really weird happened with the PR. The commit ended up on main (https://github.com/aws/aws-cdk/commit/aed8ad10c3d86497be34b2889466f770910d36ef), but the PR didn't get marked as merged. So, this is fixed and should out soon :+1:

[github-actions[bot]]

Comments on closed issues and PRs are hard for our team to see. If you need help, please open a new issue that references this one.