Setting the file. One moment.
Subchapter 7.55
references/support-topics/sveltekit-split-cold-start-tradeoff.mdMarkdown1 KBView on GitHub
SvelteKit bundles routes together by default to avoid excessive cold starts. Treat split: true as a targeted tradeoff, not a blanket optimization.
Use cold-start share, cold-vs-warm latency, deployment concentration, and source bundle pressure. Check adapter options and whether a large dependency belongs to one route or the whole app.
Do not split every route without evidence of function size pressure or route-local initialization cost. Do not split if cold starts are already the dominant problem.
Name the cold-start signal, route or dependency that motivates the split, and the exact adapter config line.