Why, with SSR, does the "/" route have to be prerendered (SSG) by default?

[nunoarruda]

According to the Prerendering routes documentation:

With SSR, the "/" route is prerendered by default.

It is a necessary step to return a rendered HTML when the user visits the root of the application. The prerendered routes can be customized, but keep in mind to include the "/" route also.

Why is that?
Wouldn't that mean that data would only be updated on the next build?
What if my "/" route (homepage / default route) has dynamic data or content that changes frequently and I want to SSR it?

I know I could just disable SSR and SSG and use the app as a regular CSR/SPA app, but my goal here is to use SSR on the homepage.

Thanks in advance for any clarification 👍

[brandonroberts]

The / is prerendered by default because most of the sites built with Analog are more content focused, so the / route is likely a landing page. You don't have to disable SSR to have a dynamically rendered / page.

Just pass an empty array to the routes array and it will use SSR for initial page requests and switch to CSR/SPA mode for navigation after that so you get the best of both.