Merge branch 'main' into llms-txt

Author: dummdidumm

apps/svelte.dev/content/docs/svelte/98-reference/.generated/client-warnings.md

@@ -204,46 +204,6 @@ Consider the following code:
 
 To fix it, either create callback props to communicate changes, or mark `person` as [`$bindable`]($bindable).
 
-### reactive_declaration_non_reactive_property
-
-```
-A `$:` statement (%location%) read reactive state that was not visible to the compiler. Updates to this state will not cause the statement to re-run. The behaviour of this code will change if you migrate it to runes mode
-```
-
-In legacy mode, a `$:` [reactive statement](https://svelte.dev/docs/svelte/legacy-reactive-assignments) re-runs when the state it _references_ changes. This is determined at compile time, by analysing the code.
-
-In runes mode, effects and deriveds re-run when there are changes to the values that are read during the function's _execution_.
-
-Often, the result is the same — for example these can be considered equivalent:
-
-```js
-let a = 1, b = 2, sum = 3;
-// ---cut---
-$: sum = a + b;
-```
-
-```js
-let a = 1, b = 2;
-// ---cut---
-const sum = $derived(a + b);
-```
-
-In some cases — such as the one that triggered the above warning — they are _not_ the same:
-
-```js
-let a = 1, b = 2, sum = 3;
-// ---cut---
-const add = () => a + b;
-
-// the compiler can't 'see' that `sum` depends on `a` and `b`, but
-// they _would_ be read while executing the `$derived` version
-$: sum = add();
-```
-
-Similarly, reactive properties of [deep state](https://svelte.dev/docs/svelte/$state#Deep-state) are not visible to the compiler. As such, changes to these properties will cause effects and deriveds to re-run but will _not_ cause `$:` statements to re-run.
-
-When you [migrate this component](https://svelte.dev/docs/svelte/v5-migration-guide) to runes mode, the behaviour will change accordingly.
-
 ### state_proxy_equality_mismatch
 
 ```

apps/svelte.dev/content/docs/svelte/98-reference/21-svelte-reactivity-window.md

@@ -47,7 +47,7 @@ on Firefox and Safari it won't.
 
 ```dts
 const devicePixelRatio: {
-	get current(): number;
+	get current(): number | undefined;
 };
 ```
 

apps/svelte.dev/content/docs/svelte/98-reference/30-runtime-warnings.md

@@ -211,46 +211,6 @@ Consider the following code:
 
 To fix it, either create callback props to communicate changes, or mark `person` as [`$bindable`]($bindable).
 
-### reactive_declaration_non_reactive_property
-
-```
-A `$:` statement (%location%) read reactive state that was not visible to the compiler. Updates to this state will not cause the statement to re-run. The behaviour of this code will change if you migrate it to runes mode
-```
-
-In legacy mode, a `$:` [reactive statement](https://svelte.dev/docs/svelte/legacy-reactive-assignments) re-runs when the state it _references_ changes. This is determined at compile time, by analysing the code.
-
-In runes mode, effects and deriveds re-run when there are changes to the values that are read during the function's _execution_.
-
-Often, the result is the same — for example these can be considered equivalent:
-
-```js
-let a = 1, b = 2, sum = 3;
-// ---cut---
-$: sum = a + b;
-```
-
-```js
-let a = 1, b = 2;
-// ---cut---
-const sum = $derived(a + b);
-```
-
-In some cases — such as the one that triggered the above warning — they are _not_ the same:
-
-```js
-let a = 1, b = 2, sum = 3;
-// ---cut---
-const add = () => a + b;
-
-// the compiler can't 'see' that `sum` depends on `a` and `b`, but
-// they _would_ be read while executing the `$derived` version
-$: sum = add();
-```
-
-Similarly, reactive properties of [deep state](https://svelte.dev/docs/svelte/$state#Deep-state) are not visible to the compiler. As such, changes to these properties will cause effects and deriveds to re-run but will _not_ cause `$:` statements to re-run.
-
-When you [migrate this component](https://svelte.dev/docs/svelte/v5-migration-guide) to runes mode, the behaviour will change accordingly.
-
 ### state_proxy_equality_mismatch
 
 ```

apps/svelte.dev/src/lib/server/content.ts

@@ -10,11 +10,14 @@ const documents = import.meta.glob<string>('../../../content/**/*.md', {
 	import: 'default'
 });
 
-const assets = import.meta.glob<string>('../../../content/**/+assets/**', {
-	eager: true,
-	query: '?url',
-	import: 'default'
-});
+const assets = import.meta.glob<string>(
+	['../../../content/**/+assets/**', '../../../content/**/+assets/**/.env'],
+	{
+		eager: true,
+		query: '?url',
+		import: 'default'
+	}
+);
 
 export const documentsContent = import.meta.glob<string>('../../../content/**/*.md', {
 	eager: true,

apps/svelte.dev/src/routes/+error.svelte

@@ -21,7 +21,7 @@
 					If you were expecting to find something here, please drop by the
 					<a href="/chat"> Discord chatroom </a>
 					and let us know, or raise an issue on
-					<a href="https://github.com/sveltejs/sites">GitHub</a>. Thanks!
+					<a href="https://github.com/sveltejs/svelte.dev/issues">GitHub</a>. Thanks!
 				</p>
 			{:else}
 				<h1>Yikes!</h1>

apps/svelte.dev/src/routes/e/tmp/codes.json/+server.ts

@@ -14,7 +14,11 @@ const codes: Record<string, Record<string, string[]>> = {};
 
 for (const page of reference) {
 	const grouped: Record<string, string[]> = {};
-	const sections = page.body.split(/(^|\n)## /g).slice(1);
+	const sections = page.body.split(/(^|\n)## /g);
+
+	if (sections.length > 1) {
+		sections.shift();
+	}
 
 	for (const section of sections) {
 		const lines = section.slice(section.startsWith('\n') ? 1 : 0).split('\n');

packages/repl/src/lib/workers/bundler/index.ts

@@ -291,7 +291,7 @@ async function get_bundle(
 				const pkg_url =
 					pkg_name === 'svelte'
 						? `${svelte_url}/package.json`
-						: `${packages_url}/${pkg_name}/package.json`;
+						: `${packages_url}/${pkg_name}@${match[2] ?? 'latest'}/package.json`;
 				const subpath = `.${match[3] ?? ''}`;
 
 				// if this was imported by one of our files, add it to the `imports` set