svelte/kit-app-state

Dlaczego

$app/stores was the Svelte 4 store version of the page state. SvelteKit 3 removed it, so an import breaks the build after the upgrade, and on Kit 2 the store does not take part in Svelte 5's fine-grained reactivity. Agents still write $page from older examples.

Poprawka

import { page, navigating, updated } from '$app/state' and drop the $ prefix: $page.url.pathname becomes page.url.pathname. These are read-only state objects, so read them in markup or in $derived. npx sv migrate sveltekit-3 rewrites most imports.

Przykłady

<!-- bad -->
<script>
  import { page } from '$app/stores'
</script>
<a href="/docs" aria-current={$page.url.pathname === '/docs' ? 'page' : undefined}>Docs</a>
<!-- good -->
<script>
  import { page } from '$app/state'
</script>
<a href="/docs" aria-current={page.url.pathname === '/docs' ? 'page' : undefined}>Docs</a>

Źródła

• SvelteKit docs, Migrating to SvelteKit v3 ($app/stores removed)
• SvelteKit docs, $app/state

Przeczytaj w terminalu

npx github:dawidolko/frontend-skills explain svelte/kit-app-state