Static rendering vs hydration for edge-deployed SvelteKit pages with runtime-dependent content
When deploying a SvelteKit application to an edge platform, pages that incorporate runtime-dependent values—such as timestamps, user-specific data, or feature flags evaluated only on the server—create a tension between two documented rendering modes. Enabling the default hydrate: true preserves client-side interactivity but risks hydration mismatches when th