Jason Miller

Update from me: we should re-test this with the dev-time SSR from #169, since it provides all of the page's modules as flat `` tags. It's not a full solution...

Hi @davezuko! Running PostCSS once is definitely in keeping with the spirit of this project. For development I do like the idea of using the existence of a PostCSS config...

Microbubble supports React already. It should be possible to switch between the two.

The following dependencies and `.babelrc` should make Microbundle work like microbundle-crl: `npm i -D @babel/plugin-proposal-optional-chaining @babel/plugin-proposal-decorators babel-plugin-inline-react-svg babel-plugin-file-loader` ```js { "plugins": [ ["transform-react-jsx", { "pragma": "React.createElement", "pragmaFrag": "React.Fragment" }], "@babel/plugin-proposal-optional-chaining",...

Reading through this and the comments makes me think such a data structure and flow could be: ```ts // A module@version string where the version is fully resolved, like "[email protected]":...

The file map within each module is important because we need it in order to handle requests for modules that haven't yet been streamed. Probably clearer in the example below,...

I'm good with the game world style approach. Only thing in your code sample I find awkward is the callback to waitFile. Based on the logic it seems like we...

Why would this plugin have any reason to support Node 4 when ESlint itself only supports Node 10+? That's a lot of baggage for no discernable gain.

Have you evaluated the performance and disk usage tradeoff this is inherently making, or is this a purely philosophical stance?

I'm not sure that viewpoint is broadly shared. Developers have hundreds of projects on a machine, and this one is just under 8mb. Anecdotally, eslint-plugin-react accounts for more than 1GB...