Niklas Mischkulnig

https://github.com/parcel-bundler/parcel/pull/8387 is going to change this to 1. autoinstall node builtin polyfills into the project root if not already installed and 2. always resolve the polyfills from the project root

We would need to process `url()` before SASS is run (similar to https://github.com/bholloway/resolve-url-loader): - either literally do that - (or use sourcemaps to find out the original asset of a...

As far as I can tell, worklets don't have `self` and one has to use `globalThis` instead. And that library simply has `self` in the output: https://unpkg.com/browse/[email protected]/dist/ort-web.js

-> https://github.com/microsoft/onnxruntime/issues/13072

It's apparently not JSON in this case: https://github.com/parcel-bundler/parcel/blob/527e477d15441219216ed05b220cf8d48fa2d258/packages/transformers/elm/src/ElmTransformer.js#L36 https://github.com/parcel-bundler/parcel/blob/527e477d15441219216ed05b220cf8d48fa2d258/packages/transformers/elm/src/ElmTransformer.js#L59-L63

~A way to reliable trigger this:~ https://github.com/parcel-bundler/parcel/issues/5965 Something else that's strange: 0. Delete `.parcel-cache`, set color to red 1. start, it's red 3. change color to blue, refresh, it's blue...

You should use two different targets (with a single source each) instead.

> building with the usual polyfills for the browser (Node builtins, replacing globals like Buffer, inlining readFileSync) while also not using the browser field for resolution Well, there's a problem...

Relevant code: https://github.com/parcel-bundler/parcel/blob/cbc84b0c1d538b0ec15a3bf01f95da3ed623ebbb/packages/reporters/dev-server/src/Server.js#L327-L350

I'm not sure why that check is there. As long as https://github.com/parcel-bundler/parcel/blob/cbc84b0c1d538b0ec15a3bf01f95da3ed623ebbb/packages/reporters/dev-server/src/Server.js#L338 handles HEAD correctly, removing that should be fine. (And another question is how a head request should behave...