Discussing caveat: "Is starting at / and crawling sufficient?"

“Is starting at / and crawling sufficient? Might there be unreachable sections of your site?”

I think for most well-structured sites this should not be an issue since you can hopefully get to every page that ever existed by just clicking through the web of links…

However, for my use case, I want react-snapshot to render a static page that is not linked from anywhere. The page is a variation of one of my form pages, but it only contains the form, not the site layout (header, footer, etc.). (Unfortunately) I use this by embedding this page in another website in an iframe. This is why it doesn’t need to be linked anywhere in the main site (it should not be crawled, but it does need to exist statically).

I know the premise of react-snapshot is to be zero-configuration so I’m not sure that my use case will be supported, but do you have any ideas how this might look?

[geelen]

I don’t mind it, but to be honest, a bit of config isn’t maybe too bad:

/* package.json */
{
  ...,
  "react-snapshot": [
    "/",
    "/form?with=params"
  ]
}

That way at least each line is nicely tracked by version control…

[geelen]

Sorry for dropping this for a while. I think in the case you describe, it probably makes more sense to make like a index page for all the URLs you can’t otherwise reach, call it like __index.html or something. If you put a hidden link on your homepage, or point react-snapshot at it directly in package.json, the crawler will find it and cache all those routes.

I think that’s better than having an executable config.