Niklas Mischkulnig

That works fine for me on macOS (Intel) with Docker Desktop.

Please provide a [small code sample that reproduces the issue](https://minimum-reproduction.wtf/).

With https://github.com/parcel-bundler/parcel/pull/9328 and https://github.com/parcel-bundler/parcel/pull/9365, if packaged/build correctly Parcel can run int he browser. The question is how we can make it use the right codepaths for WebContainers now

Ideally, `import css from "bundle-text:./my.css";` should be have like a regular JS import, so any change in `my.css` or its dependencies should trigger an HMR update that can be caught...

Related: https://github.com/parcel-bundler/parcel/issues/3942#issuecomment-569084383, https://github.com/parcel-bundler/parcel/issues/3942#issuecomment-571192655

> Or should the root .env.local be more important than the package .env.local? I'd say no.

@alessandrojcm You don't need to specify NODE_ENV explicitly in your case. `parcel build` automatically sets `production` and in watch mode, `development`. Please provide a full example.

> In my case, i solved it by adding the entrie file path in package.json. This should be fixed now in the latest nightly version by https://github.com/parcel-bundler/parcel/pull/7537 Try using `yarn...

Yes, currently it only searches for dotfiles in the project (=monorepo) root https://github.com/parcel-bundler/parcel/blob/3b3b13557dba9d1a403c86550915c6013dd78dfe/packages/core/core/src/loadDotEnv.js#L18-L35

The resolver does indeed only read tsconfig: https://github.com/parcel-bundler/parcel/blob/a2789a49b88b66c67a378b8c8813e504c77c8648/packages/utils/node-resolver-rs/src/lib.rs#L1124 The transformer reads both, but prefers tsconfig (and ignore jsconfig if both exist): https://github.com/parcel-bundler/parcel/blob/a2789a49b88b66c67a378b8c8813e504c77c8648/packages/transformers/js/src/JSTransformer.js#L204-L207