Devon Govett

Small update: in the next release we have a refactor to the error overlay to modernize it and improve performance. The expensive source mapping stuff will be done in native...

We do have web assembly builds of our native modules, e.g. https://github.com/parcel-bundler/parcel/tree/v2/packages/transformers/js/wasm. They are used on https://parcel2-repl-mischnic.vercel.app/ for example. But you have to shim a whole bunch of things, like...

Both. Parcel has a [FileSystem](https://github.com/parcel-bundler/parcel/blob/v2/packages/core/fs/src/types.js#L56) abstraction in the `@parcel/fs` package. We do all of our FS operations through that. There are two implementations: `NodeFS` and `MemoryFS`. The CLI always uses...

I would like the resolver crate to remain independent. It is useful even outside Parcel so ideally should be a standalone library and not parcel-specific plugin. I believe it is...

Why? Isn't parcel_wasm mostly a duplicate of the napi bindings? There's only a few differences that were covered by conditional compilation before.

But why do we even need separate entry points for them in the first place if they are both using napi?

@jeffposnick @jakearchibald thanks for all of your feedback! Let me start by saying this is a research project so far - nothing has been decided on our side. I'm open...

> This was one of the stated desires from the Twitter thread—it sounded like Parcel does not want to be in the business of injecting client-side JavaScript into the web...

To summarize, here's the current idea: * keep content hashing filenames, but don’t include child bundles in the hash * initial load doesn’t use service worker, gets content hashed bundles...

> Also, how does the service worker know where to get this manifest from? If it's in a consistent location, it needs to be no-cache, which means you've got a...