Allow using Parcel 2 for NodejsFunction

[blimmer]

Right now, the documentation requires running Parcel^1

aws-cdk/packages/@aws-cdk/aws-lambda-nodejs/README.md

Lines 17 to 21 in f3219c3

	```
	yarn add parcel-bundler@^1
	# or
	npm install parcel-bundler@^1
	```

There are bug fixes, such as this one (parcel-bundler/parcel#3151 (comment)) that are only made to Parcel v2 and not v1.

Use Case

The aws-xray-sdk-node package relies on async_hooks, and as described in this bug report: parcel-bundler/parcel#3151 , fails to build under Parcel ^1. @gergan actually reported on that issue that he needs a workaround specifically because of the CDK's NodejsFunction reliance on Parcel v1: parcel-bundler/parcel#3151 (comment)

Proposed Solution

Allow using Parcel ^2. I'm not sure why the docs peg to v1 right now - I'm assuming there's a reason that v2 was incompatible for some reason. If it's actually compatible with v2, then we could also update the docs referenced above.

Other

I created a sample repo to show the problem with Parcel here (see the README). I also filed DataDog/datadog-lambda-js#73 with the package that's pulling aws-xray-sdk-node for more context.

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

---

This is a 🚀 Feature Request

[jogold]

Hi @blimmer

The reason is that Parcel v2 is still in alpha (https://www.npmjs.com/package/parcel?activeTab=versions, https://github.com/parcel-bundler/parcel/projects/5).

Not totally comfortable to use an alpha version for this construct.

To be updated when Parcel officially releases v2.

[eladb]

@jogold Could we allow users to fully customize their bundling step once we have docker based bundling?

[asterikx]

In response to @eladb, I would prefer co-locating my lambdas in a lambdas folder using Lerna or a Lerna-style setup so that I have full control over bundling and what dependencies are included with each lambda.

.
├── bin
│   └── cdk.ts
├── lambdas
│   ├── node_modules 
│   ├── packages
│   │   ├── lambda-one
│   │   │   ├── node_modules
│   │   │   ├── src
│   │   │   │   └── index.ts
│   │   │   ├── package.json
│   │   │   └── tsconfig.json
│   │   └── lambda-two
│   │       ├── node_modules
│   │       ├── src
│   │       │   └── index.ts
│   │       ├── package.json
│   │       └── tsconfig.json
│   ├── lerna.json
│   ├── package.json
│   └── tsconfig.json
├── lib
│   └── app-stack.ts
├── node_modules 
├── test
│   └── app.test.ts
├── cdk.json
├── jest.config.js
├── package.json
└── tsconfig.json

Parcel would then need to bundle each lambda using the configs (package.json and tsconfig.json) in the respective Lerna package. Is something like this possible with Parcel?

[jogold]

@blimmer NodejsFunction now uses Parcel 2, see #8681

[eladb]

Can we resolve this?

[jogold]

Can we resolve this?

Yes

[blimmer]

Thank you very much! I'm looking forward to the next release to try this out 😄 🎉