Jason Miller

@tkassila hmm - are you setting breakpoints in the production build (`wmr serve`), or when running the development server (`wmr`)?

Ooooh so this is 100% a bug in the npm resolution. Does it happen on master?

Ah interesting, yeah that's kinda a funky case. A thought: what if we had the HTM plugin detect `/** @jsx h */ at the top of files and insert `htm.bind(h)`?...

I just thought of another idea: we could use the new `jsxRuntime` comment option from Babel to generate a module that pulls in a different h()/jsx().

Funky. The relevant line: ```js export { finalAssertExports as assert }; ```

This looks like an issue I was having with a specific version of the Rollup CommonJS plugin.

Indeed! (though I do think Microbundle could be much simpler)

One thing that might be worth considering though, is that it'd be pretty easy for us to add a way to do additional Rollup builds, similar to what Vite provides...

Might be interesting to support the querystring parameter - IIRC Vite supports that out-of-the-box too.

The way I'd envision this working: - code does `import './foo.svelte'`, which requests a module `/foo.svelte`. - The server middleware handles that request by first asking any plugins if they'd...