Niklas Mischkulnig

This is the UTF8 BOM, apparently common at least on Windows. Looks like Yarn strips it before parsing: https://github.com/yarnpkg/berry/blob/863a2c486e6959dc465c37972d5fa735b64ae6bd/packages/yarnpkg-core/sources/Manifest.ts#L137 npm uses a package that also handles this automatically: https://github.com/npm/json-parse-even-better-errors/blob/74c9a7e27cf4884568c8e956f37f5911f1cbec8f/index.js#L112 So...

It should be `entries`: ```diff diff --git server.js server.js index 695409a..f931abc 100644 --- server.js +++ server.js @@ -3,7 +3,7 @@ const { join } = require('path'); const bundler = new...

If you build a library with Parcel and then also build use that library, we prioritize `browser` before any other field. Then you get a build error about not using...

Huh, I'll have to try it with Edge as some point, works on Chrome macOS: I haven't had time to look at this in detail yet, but: > Although perhaps...

Please provide a complete code example that produces this error

In @TobiasSchikora's case the problem is that it generates a shared CSS bundle, and one CSS bundle specific to just one of the entries. And because doing `parcel build something.js`...

Apparently it doesn't create a shared bundle.

Reproduction: ```js // index.js const x = import("./x.js"); console.log(x); // x.js module.exports = function exports() {}; ``` Outputs: ```js parcelRequire.register("j0Joe", function(module, exports) { module.exports = function module.exports() {}; }); ```...

Is there a reason you don't always pass `pipeline: 'raw'` (and remove that js/json extension check)?

Don't worry about the HMR tests, they're flakey.