Ryan Christian

> Do you plan to add this to the documentation? I have #1611 to track this, though my list of things to do is exceptionally long at the moment. It'd...

Sorry, could use some extra docs there, but feel free to add. If you look, preact-www uses `preact build --prerenderUrls src/prerender.js ...` as its build command, which leads [here](https://github.com/preactjs/preact-www/blob/master/src/prerender.js). `preRenderData.description`...

Which template are you using, or is a custom one? The first thing that comes to mind is if you have an existing service worker for `http:/loclahost:8080/` that's throwing things...

Do you have any other browsers to test with? A quick google shows other people getting that with Chrome canary/beta channels. Edit: I'm assuming you're on beta, as your user...

As far as I can tell it looks to be a Chrome bug. Honestly not sure. I don't see what would cause issues there.

You should be able to add `--no-sw` to your run commands to get around this on Beta/ > v88. You won't get the debug SW on dev, but this probably...

Well `--sw` would enable the production service worker which you definitely wouldn't want if the debug already is causing issues, though it does look like you found a bug there....

The dev mode SW is just there to disable the production one that you may test out with, so it isn't a full SW and that's where this error stems...

Closing this out as I've never been able to reproduce nor have I heard anything else regarding this in over a year.

The actual error comes from `mini-css-extract-plugin`, but your issues arise from your router. Dynamically importing components by their file path evidently causes some issues. Changing this to a more conventional...