breaking: remove stores

.changeset/quick-badgers-notice.md

@@ -0,0 +1,5 @@
+---
+'@sveltejs/kit': major
+---
+
+breaking: remove `$app/stores`

documentation/docs/20-core-concepts/10-routing.md

@@ -157,9 +157,6 @@ If an error occurs during `load`, SvelteKit will render a default error page. Yo
 <h1>{page.status}: {page.error.message}</h1>
 ```
 
-> [!LEGACY]
-> `$app/state` was added in SvelteKit 2.12. If you're using an earlier version or are using Svelte 4, use `$app/stores` instead.
-
 SvelteKit will 'walk up the tree' looking for the closest error boundary — if the file above didn't exist it would try `src/routes/blog/+error.svelte` and then `src/routes/+error.svelte` before rendering the default error page. If _that_ fails (or if the error was thrown from the `load` function of the root `+layout`, which sits 'above' the root `+error`), SvelteKit will bail out and render a static fallback error page, which you can customise by creating a `src/error.html` file.
 
 If the error occurs inside a `load` function in `+layout(.server).js`, the closest error boundary in the tree is an `+error.svelte` file _above_ that layout (not next to it).

documentation/docs/20-core-concepts/20-load.md

@@ -171,10 +171,6 @@ In some cases, we might need the opposite — a parent layout might need to acce
 
 Type information for `page.data` is provided by `App.PageData`.
 
-> [!LEGACY]
-> `$app/state` was added in SvelteKit 2.12. If you're using an earlier version or are using Svelte 4, use `$app/stores` instead.
-> It provides a `page` store with the same interface that you can subscribe to, e.g. `$page.data.title`.
-
 ## Universal vs server
 
 As we've seen, there are two types of `load` function:

documentation/docs/20-core-concepts/50-state-management.md

@@ -82,7 +82,7 @@ If you're not using SSR, then there's no risk of accidentally exposing one user'
 
 ## Using state and stores with context
 
-You might wonder how we're able to use `page.data` and other [app state]($app-state) (or [app stores]($app-stores)) if we can't use global state. The answer is that app state and app stores on the server use Svelte's [context API](/tutorial/svelte/context-api) — the state (or store) is attached to the component tree with `setContext`, and when you subscribe you retrieve it with `getContext`. We can do the same thing with our own state:
+You might wonder how we're able to use `page.data` and other [app state]($app-state) if we can't use global state. The answer is that app state and app stores on the server use Svelte's [context API](/tutorial/svelte/context-api) — the state (or store) is attached to the component tree with `setContext`, and when you subscribe you retrieve it with `getContext`. We can do the same thing with our own state:
 
 ```svelte
 <!--- file: src/routes/+layout.svelte --->

documentation/docs/30-advanced/25-errors.md

@@ -51,9 +51,6 @@ This throws an exception that SvelteKit catches, causing it to set the response
 <h1>{page.error.message}</h1>
 ```
 
-> [!LEGACY]
-> `$app/state` was added in SvelteKit 2.12. If you're using an earlier version or are using Svelte 4, use `$app/stores` instead.
-
 You can add extra properties to the error object if needed...
 
 ```js

documentation/docs/30-advanced/67-shallow-routing.md

@@ -37,9 +37,6 @@ The second argument is the new page state, which can be accessed via the [page o
 
 To set page state without creating a new history entry, use `replaceState` instead of `pushState`.
 
-> [!LEGACY]
-> `page.state` from `$app/state` was added in SvelteKit 2.12. If you're using an earlier version or are using Svelte 4, use `$page.state` from `$app/stores` instead.
-
 ## Loading data for a route
 
 When shallow routing, you may want to render another `+page.svelte` inside the current page. For example, clicking on a photo thumbnail could pop up the detail view without navigating to the photo page.

documentation/docs/98-reference/20-$app-state.md

@@ -4,7 +4,4 @@ title: $app/state
 
 SvelteKit makes three read-only state objects available via the `$app/state` module — `page`, `navigating` and `updated`.
 
-> [!NOTE]
-> This module was added in 2.12. If you're using an earlier version of SvelteKit, use [`$app/stores`]($app-stores) instead.
-
 > MODULE: $app/state

documentation/docs/98-reference/20-$app-stores.md

@@ -2,6 +2,4 @@
 title: $app/stores
 ---
 
-This module contains store-based equivalents of the exports from [`$app/state`]($app-state). If you're using SvelteKit 2.12 or later, use that module instead.
-
-> MODULE: $app/stores
+This module contained store-based equivalents of the exports from [`$app/state`]($app-state) but was removed in 3.0. 

packages/kit/scripts/generate-dts.js

@@ -13,8 +13,7 @@ await createBundle({
 		'$app/navigation': 'src/runtime/app/navigation.js',
 		'$app/paths': 'src/runtime/app/paths/public.d.ts',
 		'$app/server': 'src/runtime/app/server/index.js',
-		'$app/state': 'src/runtime/app/state/index.js',
-		'$app/stores': 'src/runtime/app/stores.js'
+		'$app/state': 'src/runtime/app/state/index.js'
 	},
 	include: ['src']
 });

packages/kit/src/core/sync/write_root.js

@@ -81,45 +81,29 @@ export function write_root(manifest_data, config, output) {
 			<!-- This file is generated by @sveltejs/kit — do not edit it! -->
 			<svelte:options runes={true} />
 			<script>
-				import { setContext, onMount, tick } from 'svelte';
-				import { browser } from '$app/environment';
+				import { tick } from 'svelte';
 
-				// stores
-				let { stores, page, constructors, components = [], form, ${use_boundaries ? 'errors = [], error, ' : ''}${levels
+				let { page, constructors, components = [], form, ${use_boundaries ? 'errors = [], error, ' : ''}${levels
 					.map((l) => `data_${l} = null`)
 					.join(', ')} } = $props();
 				${use_boundaries ? `let data = $derived({${levels.map((l) => `'${l}': data_${l}`).join(', ')}})` : ''}
 
-				if (browser) {
-					$effect.pre(() => stores.page.set(page));
-				} else {
-					// svelte-ignore state_referenced_locally
-					setContext('__svelte__', stores);
-					// svelte-ignore state_referenced_locally
-					stores.page.set(page);
-				}
-
-				$effect(() => {
-					stores;page;constructors;components;form;${use_boundaries ? 'errors;error;' : ''}${levels.map((l) => `data_${l}`).join(';')};
-					stores.page.notify();
-				});
-
 				let mounted = $state(false);
 				let navigated = $state(false);
 				let title = $state(null);
 
-				onMount(() => {
-					const unsubscribe = stores.page.subscribe(() => {
-						if (mounted) {
-							navigated = true;
-							tick().then(() => {
-								title = document.title || 'untitled page';
-							});
-						}
-					});
+				let initialised = false;
 
+				$effect(() => {
+					page;
+					if (initialised) {
+						navigated = true;
+						tick().then(() => {
+							title = document.title || 'untitled page';
+						});
+					}
 					mounted = true;
-					return unsubscribe;
+					initialised = true;
 				});
 
 				const Pyramid_${max_depth} = $derived(constructors[${max_depth}]);

packages/kit/src/exports/index.js

@@ -14,19 +14,6 @@ import { text_encoder } from '../runtime/utils.js';
 
 export { VERSION } from '../version.js';
 
-// TODO 3.0: remove these types as they are not used anymore (we can't remove them yet because that would be a breaking change)
-/**
- * @template {number} TNumber
- * @template {any[]} [TArray=[]]
- * @typedef {TNumber extends TArray['length'] ? TArray[number] : LessThan<TNumber, [...TArray, TArray['length']]>} LessThan
- */
-
-/**
- * @template {number} TStart
- * @template {number} TEnd
- * @typedef {Exclude<TEnd | LessThan<TEnd>, LessThan<TStart>>} NumericRange
- */
-
 // Keep the status codes as `number` because restricting to certain numbers makes it unnecessarily hard to use compared to the benefits
 // (we have runtime errors already to check for invalid codes). Also see https://github.com/sveltejs/kit/issues/11780
 
@@ -137,8 +124,6 @@ export function isRedirect(e) {
  * @deprecated use `Response.json`
  */
 export function json(data, init) {
-	// TODO deprecate this in favour of `Response.json` when it's
-	// more widely supported
 	const body = JSON.stringify(data);
 
 	// we can't just do `text(JSON.stringify(data), init)` because

packages/kit/src/exports/public.d.ts

@@ -1367,7 +1367,7 @@ export type AfterNavigate = (Navigation | NavigationEnter) & {
 };
 
 /**
- * The shape of the [`page`](https://svelte.dev/docs/kit/$app-state#page) reactive object and the [`$page`](https://svelte.dev/docs/kit/$app-stores) store.
+ * The shape of the [`page`](https://svelte.dev/docs/kit/$app-state#page) reactive object.
  */
 export interface Page<
 	Params extends AppLayoutParams<'/'> = AppLayoutParams<'/'>,

packages/kit/src/runtime/app/state/client.js

@@ -3,7 +3,6 @@ import {
 	navigating as _navigating,
 	updated as _updated
 } from '../../client/state.svelte.js';
-import { stores } from '../../client/client.js';
 
 export const page = {
 	get data() {
@@ -57,5 +56,5 @@ export const updated = {
 	get current() {
 		return _updated.current;
 	},
-	check: stores.updated.check
+	check: _updated.check
 };