Jason Miller

The only places it would could be that Microbundle looks it would be: `babel.config.js` `.babelrc` (or `.babelrc.*`) `package.json` "babel" field Another (wild) possibility: Babel searches all the way up the...

I left a solution for the render-to-string piece over on [your preact-router issue](https://github.com/preactjs/preact-router/issues/402#issuecomment-1017962646). As @JoviDeCroock mentioned, WMR doesn't provide an SSR runtime (currently), so status codes are entirely up to...

This should have been fixed by #525.

Possibly - they have to be published independently of the main package, but that doesn't seem like a huge issue. In the case of this SSR thing I'm not sure...

This is a tricky one - in development, there is no such think as an entry module, and we don't run any bundle-related plugin methods. One option would be to...

container.options is the current options object, it's different from plugin.options.

FWIW I ventured further down this path in 8960114 and I think the output size savings are worth the breakage possibility you mentioned. It's worth us warning about it though,...

This might be slightly on the side of personal preference, but here's my reason for not using `runtime`: when building small libraries for the browser, importing a single tiny function...

There are two levels of fix here: the easy quick fix is to remove (and stop recommending usage of) the specific entry modules from `preact-iso` (so never import `preact-iso/router`). The...

@danielweck Right - the issue here is still present even when using the exports correctly: ``` import lazy, { ErrorBoundary } from 'preact-iso/lazy'; // imports a bundled copy of `preact-iso/lazy`...