fix

Author: dummdidumm

documentation/docs/98-reference/30-compiler-errors.md

@@ -263,7 +263,6 @@ Cannot reference store value outside a `.svelte` file
 
 Using a `$` prefix to refer to the value of a store is only possible inside `.svelte` files, where Svelte can automatically create subscriptions when a component is mounted and unsubscribe when the component is unmounted. Consider migrating to runes instead.
 
-
 ## typescript_invalid_feature
 
 ```
@@ -633,11 +632,11 @@ Mixing old (on:%name%) and new syntaxes for event handling is not allowed. Use o
 %thing% is invalid inside `<%parent%>`
 ```
 
+HTML restricts where certain elements can appear. In case of a violation the browser will 'repair' the HTML in a way that breaks Svelte's assumptions about the structure of your components. Some examples:
+
 - `<p>hello <div>world</div></p>` will result in `<p>hello </p><div>world</div><p></p>` for example (the `<div>` autoclosed the `<p>` because `<p>` cannot contain block-level elements)
 - `<option><div>option a</div></option>` will result in `<option>option a</option>` (the `<div>` is removed)
 - `<table><tr><td>cell</td></tr></table>` will result in `<table><tbody><tr><td>cell</td></tr></tbody></table>` (a `<tbody>` is auto-inserted)
-HTML restricts where certain elements can appear. In case of a violation the browser will 'repair' the HTML in a way that breaks Svelte's assumptions about the structure of your components. Some examples:
-
 
 ## render_tag_invalid_call_expression
 
@@ -869,7 +868,6 @@ Tag name must be lowercase and hyphenated
 
 See https://html.spec.whatwg.org/multipage/custom-elements.html#valid-custom-element-name for more information on valid tag names
 
-
 ## svelte_options_reserved_tagname
 
 ```
@@ -878,7 +876,6 @@ Tag name is reserved
 
 See https://html.spec.whatwg.org/multipage/custom-elements.html#valid-custom-element-name for more information on valid tag names
 
-
 ## svelte_options_unknown_attribute
 
 ```

documentation/docs/98-reference/30-compiler-warnings.md

@@ -450,12 +450,13 @@ Using `on:%name%` to listen to the %name% event is deprecated. Use the event att
 %thing% is invalid inside `<%parent%>`. When rendering this component on the server, the resulting HTML will be modified by the browser, likely resulting in a `hydration_mismatch` warning
 ```
 
-This code will work when the component is rendered on the client (which is why this is a warning rather than an error), but if you use server rendering it will cause hydration to fail.
+HTML restricts where certain elements can appear. In case of a violation the browser will 'repair' the HTML in a way that breaks Svelte's assumptions about the structure of your components. Some examples:
+
 - `<p>hello <div>world</div></p>` will result in `<p>hello </p><div>world</div><p></p>` for example (the `<div>` autoclosed the `<p>` because `<p>` cannot contain block-level elements)
 - `<option><div>option a</div></option>` will result in `<option>option a</option>` (the `<div>` is removed)
 - `<table><tr><td>cell</td></tr></table>` will result in `<table><tbody><tr><td>cell</td></tr></tbody></table>` (a `<tbody>` is auto-inserted)
-HTML restricts where certain elements can appear. In case of a violation the browser will 'repair' the HTML in a way that breaks Svelte's assumptions about the structure of your components. Some examples:
 
+This code will work when the component is rendered on the client (which is why this is a warning rather than an error), but if you use server rendering it will cause hydration to fail.
 
 ## script_context_deprecated
 
@@ -481,6 +482,24 @@ Using `<slot>` to render parent content is deprecated. Use `{@render ...}` tags
 `<svelte:component>` is deprecated in runes mode — components are dynamic by default
 ```
 
+In previous versions of Svelte, the component constructor was fixed when the component was rendered. In other words, if you wanted `<X>` to re-render when `X` changed, you would either have to use `<svelte:component this={X}>` or put the component inside a `{#key X}...{/key}` block.
+
+In Svelte 5 this is no longer true — if `X` changes, `<X>` re-renders.
+
+In some cases `<object.property>` syntax can be used as a replacement; a lowercased variable with property access is recognized as a component in Svelte 5.
+
+For complex component resolution logic, an intermediary, capitalized variable may be necessary. E.g. in places where `@const` can be used:
+
+```diff
+{#each items as item}
+-	<svelte:component this={item.condition ? Y : Z} />
++	{@const Component = item.condition ? Y : Z}
++	<Component />
+{/each}
+```
+
+A derived value may be used in other contexts:
+
 ```diff
 <script>
 	...
@@ -490,19 +509,6 @@ Using `<slot>` to render parent content is deprecated. Use `{@render ...}` tags
 - <svelte:component this={condition ? Y : Z} />
 + <Component />
 ```
-A derived value may be used in other contexts:
-```diff
-{#each items as item}
--	<svelte:component this={item.condition ? Y : Z} />
-+	{@const Component = item.condition ? Y : Z}
-+	<Component />
-{/each}
-```
-For complex component resolution logic, an intermediary, capitalized variable may be necessary. E.g. in places where `@const` can be used:
-In some cases `<object.property>` syntax can be used as a replacement; a lowercased variable with property access is recognized as a component in Svelte 5.
-In Svelte 5 this is no longer true — if `X` changes, `<X>` re-renders.
-In previous versions of Svelte, the component constructor was fixed when the component was rendered. In other words, if you wanted `<X>` to re-render when `X` changed, you would either have to use `<svelte:component this={X}>` or put the component inside a `{#key X}...{/key}` block.
-
 
 ## svelte_element_invalid_this
 

documentation/docs/98-reference/30-runtime-warnings.md

@@ -18,9 +18,9 @@ generated: 'generated by process-messages/index.js'
 Your `console.%method%` contained `$state` proxies. Consider using `$inspect(...)` or `$state.snapshot(...)` instead
 ```
 
-The easiest way to log a value as it changes over time is to use the [`$inspect`](https://svelte-5-preview.vercel.app/docs/runes#$inspect) rune. Alternatively, to log things on a one-off basis (for example, inside an event handler) you can use [`$state.snapshot`](https://svelte-5-preview.vercel.app/docs/runes#$state-snapshot) to take a snapshot of the current value.
 When logging a [proxy](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy), browser devtools will log the proxy itself rather than the value it represents. In the case of Svelte, the 'target' of a `$state` proxy might not resemble its current value, which can be confusing.
 
+The easiest way to log a value as it changes over time is to use the [`$inspect`](https://svelte-5-preview.vercel.app/docs/runes#$inspect) rune. Alternatively, to log things on a one-off basis (for example, inside an event handler) you can use [`$state.snapshot`](https://svelte-5-preview.vercel.app/docs/runes#$state-snapshot) to take a snapshot of the current value.
 
 ## event_handler_invalid
 
@@ -85,16 +85,18 @@ Mutating a value outside the component that created it is strongly discouraged.
 Reactive `$state(...)` proxies and the values they proxy have different identities. Because of this, comparisons with `%operator%` will produce unexpected results
 ```
 
-To resolve this, ensure you're comparing values where both values were created with `$state(...)`, or neither were. Note that `$state.raw(...)` will _not_ create a state proxy.
-	value === proxy; // always false
-</script>
-```
+`$state(...)` creates a [proxy](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy) of the value it is passed. The proxy and the value have different identities, meaning equality checks will always return `false`:
+
 ```svelte
 <script>
 	let value = { foo: 'bar' };
 	let proxy = $state(value);
-`$state(...)` creates a [proxy](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy) of the value it is passed. The proxy and the value have different identities, meaning equality checks will always return `false`:
 
+	value === proxy; // always false
+</script>
+```
+
+To resolve this, ensure you're comparing values where both values were created with `$state(...)`, or neither were. Note that `$state.raw(...)` will _not_ create a state proxy.
 
 ## dynamic_void_element_content
 
@@ -109,6 +111,5 @@ Value cannot be cloned with `$state.snapshot` — the original value was returne
 ```
 ```
 The following properties cannot be cloned with `$state.snapshot` — the return value contains the originals:
-
 %properties%
 ```

packages/svelte/scripts/process-messages/index.js

@@ -31,10 +31,29 @@ for (const category of fs.readdirSync('messages')) {
 
 			sorted.push({ code, _ });
 
-			const sections = text.trim().split('\n\n');
+			const lines = text.trim().split('\n');
+			let current_section = '';
+			let sections = [];
 			let details = '';
-			while (!sections[sections.length - 1].startsWith('> ')) {
-				details += /** @type {string} */ (sections.pop()) + '\n';
+
+			for (let i = 0; i < lines.length; i++) {
+				const line = lines[i];
+
+				if (line.startsWith('> ')) {
+					current_section += line.slice(2) + '\n';
+				} else if (line === '' && lines[i + 1]) {
+					if (lines[i + 1].startsWith('> ')) {
+						sections.push(current_section.trim());
+						current_section = '';
+					} else {
+						details = lines.slice(i + 1).join('\n');
+						break;
+					}
+				}
+			}
+
+			if (current_section.length > 0) {
+				sections.push(current_section.trim());
 			}
 
 			if (sections.length === 0) {
@@ -43,8 +62,8 @@ for (const category of fs.readdirSync('messages')) {
 
 			seen.add(code);
 			messages[category][code] = {
-				messages: sections.map((section) => section.replace(/^> /gm, '').replace(/^>\n/gm, '\n')),
-				details
+				messages: sections,
+				details: details
 			};
 		}