SvelteKit 3 RC Resets Framework Contracts — Week 33 JavaScript

TanStack Router's loading rewrite separates four lifetimes that a single navigation promise used to blur. A loader flight and lease count decide whether shared work should continue; the current transaction decides which navigation may publish; a private lane reduces parallel loader results; and a framework receipt records whether React, Solid, or Vue actually committed the publication. A redirect remains control flow and can suppress an earlier error without publishing its route branch. Losing publication authority does not automatically abort a loader still needed by a preload or cache. The model addresses recurring bugs in cancellation, redirects, pending UI, SSR, caching, and render acknowledgements.

Angular 22 makes injectAsync stable, allowing a heavy auto-provided service to live in its own dynamic-import chunk and resolve through ordinary dependency injection on first use. Angular caches the promise, so later calls reuse the instance without another request. The service must use @Injectable({ providedIn: 'root' }) or @Service(); manually scoped providers are not eligible. onIdle can prefetch the chunk, while a custom promise trigger can react to pointer or keyboard focus before a button is clicked. The example removes a roughly 33 kB development chunk from startup, but small or frequently used services may cost more in latency and async complexity than they save.

Overlapping optimistic writes can lose an earlier change even when Next.js dispatches Server Actions sequentially, because each next state may have been calculated before the previous save completed. Aurora Scharff uses useActionState as a queue whose callback receives the last confirmed state, and useOptimistic to apply the same pure reducer immediately on screen. If a save fails, returning the prior confirmed state rolls the UI back without constructing an inverse action. For calendar state shared across Server Component boundaries, a provider stores pending changes rather than duplicating the server-owned events. Client data libraries remain appropriate when data changes independently through polling or realtime updates.