Ryan Christian

> The only thing I can think of that might be different if you build the package is that we're stuck on a fairly old node (16.10.0) and npm (6.14.15)...

Looks like this is reproducible with a much smaller input: ```jsx export function Foo() { return 'Foo'; } ``` As you say, a 44 space offset in the generated file...

Found it: https://github.com/developit/microbundle/blob/105a09b9aa686ac46dc728e774d7ae3aef00aed8/src/index.js#L651-L668 We replace `globalThis` in UMD bundles, but don't correct the sourcemaps afterwards. Will try to get a fix together later.

Microbundle is a tool for building libraries, not apps. So again, wrong layer as this should be implemented in the tools that consume Microbundle's output. Also, I don't think opening...

> This context from the other thread that explains why I opened it here: > >> Fair enough. Well you may or may not find this issue relevant there then,...

I still think this should be done on the bundler/app/user side of things, rather than in libraries, but if you want to contribute a fix, go for it. --- >...

> Do you have a preference for how I implement this? Should it be a default on, and/or added as a new configurable option, etc? Sorry, meant to say that...

The name matches your output JS, I believe. If you want to name it something else you'll need to use a post-build script: ``` "build": "microbundle ... && mv dist/index.css...

@machao7 You can subscribe to the issue and get notified whenever there's progress. When there is, you'd see it here. Honestly I'd recommend avoiding the browser field spec anyhow, `package.json#exports`...

I don't believe that's possible now, no.