Documentation for catch-all page

[chrisvfritz]

Documentation for catch-all page

[chrisvfritz]

This is outside the responsibility of the plugin. When I've wanted this in the past, I just have Webpack create an extra copy of my HTML template as fallback.html or similar.

[drewlustro]

@jdrydn - Excellent work!

If you want to add this to the documentation README.md in a PR, by all means ;)

[jdrydn]

Yeah, I figured this was outside the scope of this plugin, I just wanted to be certain.

Perhaps a note in the caveats section of your README explaining "if you pre-render the root (/) the index.html page will be overridden, so you should use webpack to create another fallback.html..."? Your docs are absolutely fab otherwise 😍

Oh, and 👍 for this plugin, it's ace!

[chrisvfritz]

Yeah, I agree that'd make a great addition to the documentation. I just retitled and opened this issue. I'll update the docs when it's not 3am. 😄 Glad you're enjoying it!

[drewlustro]

Let me know if you plan to handle this, @chrisvfritz 👍 👍

[chrisvfritz]

@drewlustro No, feel free to. 😅

[jdrydn]

I've been poked a few times about how I "solved" this, with two people referencing this issue directly, so I'll pop this here:

I duplicated the HtmlWebpackPlugin plugin in my production webpack config to generate 404.html as well as index.html, and then I would serve that 404 page on non-prerendered routes and Vue (and vue-router) takes over!

[stereobooster]

The fallback page can be named 200.html. Some static host providers use this convention, for example, surge.sh (actually I do not know any other examples). 200.html for 200 response, 404.html for 404 response.