Devon Govett

In development we don't use esm, so this is intentional. What is broken about it for you?

It shouldn't matter. ESM is just a syntax. What parcel outputs is an implementation detail that shouldn't affect the behavior of your source code. > Development should use ESM so...

The ESM format does not affect whether you bundle or don't bundle. Those are separate concerns. You can bundle both ESM and non-ESM or not bundle both ESM and non-ESM....

> I'm confused, parcel watch and parcel build having totally differently functioning outputs is intentional? That's always been the case. Minification, tree shaking, and lots of other stuff doesn't run...

TLA support is a different issue: #4028. Unfortunately it's quite difficult to implement. > I don't see the bundle as necessary whatsoever in development You would definitely notice the performance...

We no longer remove `type="module"` due to changes in #10043. The actual JS output is still pretty much the same but it now runs in a module environment.

Hmm yeah that should probably be an InvalidSpecifier error instead of UnknownError. I'd also like to have more details in the error about how to enable package exports support.

Yeah I think it doesn't work in the wasm build yet. We'd need to do something like lightningcss using the asyncify transform to support async functions called from rust. https://github.com/parcel-bundler/lightningcss/blob/master/wasm/async.mjs

Do we need a new dependency priority here? It seems very similar to the `parallel` priority we already have – the dependency should load with the parent bundle group rather...

IMO we need to hide them to keep the example code to a reasonable length. Maybe we can put in a collapsed section but I didn't think anyone would really...