Setting the file. One moment.
Subchapter 7.54
references/support-topics/sveltekit-isr-prerender-safety.mdMarkdown1 KBView on GitHub
For SvelteKit, the right lever is often prerender or adapter ISR on public consumer pages. First prove every visitor can safely see the same response for the configured interval.
Inspect +page, +page.server, +server, layouts, prerender, ssr, and adapter isr config. Compare route cache results, ISR writes, and whether the route reads cookies, auth, or per-user locals.
Do not use ISR for dashboards, carts, checkout, account data, drafts, or any route whose output varies per visitor. Do not add ISR when prerender = true already makes it irrelevant.
Name the route, current SvelteKit page option or adapter config, observed cache or ISR signal, and the exact file line to change.