Ryan Christian

Standard debugging procedure: take things apart from the top down. Router was basically the first stop, and your method of doing so was quite bizarre, so it was something I...

Oh it's certainly no problem. Let me know if a minor PR could help. > And how do I fix mini-css plugin error? The router should be altered/refactored, that should...

I sent you a PR, figured I had it already and it better outlines what I mean. Take a look if you have a chance. Definitely don't feel the need...

As far as I know there is no current plan in motion for doing so, no. It'd certainly be a nice-to-have, but there's at least a few dependencies that need...

Preact-CLI isn't necessarily unmaintained, as you can see via the commit history, work has been done recently. But keeping up with the rapidly changing Webpack ecosystem is extremely time consuming...

@FrantzUml You're confusing "deprecated" with "older versions". Few packages actually are deprecated, none with actual issues from that deprecation. Usually just maintainers giving a nudge to upgrade, which is totally...

> make an npm audit once installed and you'll see 68 packages with high level security. `npm audit` is one of the most horribly flawed pieces of software out there....

Sorry, are you saying the error message changed upon upgrading preact-cli to v3.3.5 / past 3.3.3? Makes sense that Firebase may not be suitable in Node when we prerender, but...

Gotcha! Just needed a sanity check as I couldn't imagine how an error message would change given our past few changes here. That would probably indicate something got touched that...

If you want the `serve` command to always build the application, just change the command to run `build` first, like this: ``` "build": "preact build", "serve": "yarn build && sirv...