SvelteKit 2.68.0

SvelteKit 2.68.0 has been published — the latest minor release of the Svelte-based meta-framework brings a new prerendering option and a series of bug fixes.

What Changed

The headline feature in 2.68.0 is the new prerender.handleInvalidUrl option, which gives developers finer control over how SvelteKit handles invalid URLs discovered during prerendering. Previously, encountering an invalid URL during a prerender crawl would either error out or require workarounds. Now you can define custom behavior for these edge cases.

Why It Matters

For sites that prerender heavily — documentation, marketing pages, e-commerce catalogs — the new option prevents build failures when external links or dynamically-generated paths are not reachable at build time. Developers can choose to log, warn, or silently skip invalid URLs, making CI pipelines more resilient.

Other Improvements

• Fixed support for exactOptionalPropertyTypes in optional form schemas
• Error messages now surface more clearly when prerendering auth-protected routes
• Internal performance optimizations for chunk file naming and URL handling

What is Next

The Svelte team continues to iterate on SvelteKit 2.x while development on SvelteKit 3.0 progresses in the canary channel. For now, 2.68.0 is a safe, incremental improvement for teams already on the 2.x line. Upgrade with your package manager of choice and run your test suite — the migration is straightforward.