Jason Miller

FWIW Webpack 5 actually includes disk-backed caching, which is basically what the original proposal hints at. We could try it here to see if it's an improvement for build times.

Does this still happen in the `3.0.0` release?

I created a solution for `styled-components` that adds support for stylesheet SSR in preact-cli, and doesn't really require any special configuration or tweaks (aside from defining an `SSR` constant that...

@RyanChristian4427 - I wonder if it'd be worth having CLI infer the `publicPath` value for MiniCssExtract from the config? Something like this to replace [these lines](https://github.com/preactjs/preact-cli/blob/5d7a37f059f227ab6b7b3f2066e53c44317b9704/packages/cli/lib/lib/webpack/webpack-base-config.js#L230): ```js use: [ isWatch...

Can't this just always use `__webpack_public_path__`? It defaults to `"/"`.

@prbxr is your Chrome running in a different virtual desktop or workspace? Chrome throttles backgrounded tabs, which includes things requestAnimationFrame and timers - perhaps the in-browser portion of Webpack is...

Just a note - we are generally recommending folks use preact-cli v3 in all cases. It'll become the official release in a week or so.

In @smurfb's output I can see malformed CSS that will cause the parser to fail: ``` @media (hover: hover) { } ``` Any idea where that's coming from? It doesn't...

@prateekbh yeah that's definitely a better experience here. Honestly even if we just caught the error and output something like we do for prerendering errors: > Warning: unable to inline...

The API as described should address my needs nicely! Basically declarative cache URL rewrites and external whitelisting. Happy to see regexes as the matchers. Regarding path-to-regexp, i don't know if...