Jason Miller

Did you ever find the root cause for this? There isn't really anything in prerender-loader that seems like it would cause this. Maybe it's an issue with React 16.7 +...

This project isn't dead, the fork just needs to be a Pull Request. Happy to review if anyone takes the time to do that...

That makes it a bit more difficult. I'm assuming these are functional changes?

Hmm - I think it should be there? That gets into one of the weirder issues with `DefinePlugin` - it leaks into parent compiler instances, but perhaps it doesn't leak...

IIRC you can use `self.PRERENDER`

Hi @NirBenya - can you try with the latest update I just published? Cheers.

Perhaps we need to whitelist ExtractTextPlugin here like we do for MiniCssExtractPlugin? https://github.com/GoogleChromeLabs/prerender-loader/blob/317993c3d91de937387afc19e8d13cca33539119/src/index.js#L104

Since the plugin only does prerendering of a source, the way to go here would be to create an instance of HtmlWebpackPlugin for each route. You can see how `preact-cli`...

yup! each with their own independent static HTML (and initial state, titles, etc that you might have injected during prerendering). I just amended the example with a `name` configuration value...

Update: you can now also configure JSDOM to report custom URLs for `location.href`, etc via the `documentUrl` loader option.