Svelte's monthly roundup for August confirms that the first `@next` preview releases of SvelteKit 3 shipped through July, thirteen preview versions in all, giving developers an early look at what the next major version of the framework changes. The most consequential shift is around navigation and state: shallow routing is now built directly into `goto` via a new `state` option with a `persistState` flag, replacing the separate `pushState`/`replaceState` APIs, and `refreshAll` is introduced to replace the now-deprecated `invalidateAll`. Two new modules, `$app/manifest` and `$app/service-worker`, expose build output details like immutable assets and prerendered routes at runtime and make SvelteKit's internals usable from within service workers, which previously required workarounds. SvelteKit also now proactively detects new deployments through data, remote, and form action responses as well as tab focus and visibility changes, an incremental but practical fix for the classic problem of users sitting on a stale deployed version of a site after a new release goes out. Outside the SvelteKit 3 preview, the stable line picked up a `submitted` property on remote forms so developers can react to form submission before a response comes back, and error pages now get automatic typing for their `page` and `error` props with no manual setup. For teams already on SvelteKit, none of this is disruptive since it lives in a prerelease channel, but it is a concrete signal of where the framework is heading and a chance to flag breaking changes early, before SvelteKit 3 stabilizes.