sync docs

Author: github-actions[bot]

apps/svelte.dev/content/docs/svelte/03-template-syntax/[email protected]

@@ -161,3 +161,7 @@ function foo(+++getBar+++) {
 ## Creating attachments programmatically
 
 To add attachments to an object that will be spread onto a component or element, use [`createAttachmentKey`](svelte-attachments#createAttachmentKey).
+
+## Converting actions to attachments
+
+If you're using a library that only provides actions, you can convert them to attachments with [`fromAction`](svelte-attachments#fromAction), allowing you to (for example) use them with components.

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

@@ -34,6 +34,22 @@ function add() {
 }
 ```
 
+### await_reactivity_loss
+
+```
+Detected reactivity loss
+```
+
+TODO
+
+### await_waterfall
+
+```
+An async value (%location%) was not read immediately after it resolved. This often indicates an unnecessary waterfall, which can slow down your app.
+```
+
+TODO
+
 ### binding_property_non_reactive
 
 ```

apps/svelte.dev/content/docs/svelte/98-reference/.generated/compile-errors.md

@@ -480,6 +480,12 @@ Expected token %token%
 Expected whitespace
 ```
 
+### experimental_async
+
+```
+Cannot use `await` in deriveds and template expressions, or at the top level of a component, unless the `experimental.async` compiler option is `true`
+```
+
 ### export_undefined
 
 ```
@@ -534,6 +540,12 @@ The arguments keyword cannot be used within the template or at the top level of
 %message%
 ```
 
+### legacy_await_invalid
+
+```
+Cannot use `await` in deriveds and template expressions, or at the top level of a component, unless in runes mode
+```
+
 ### legacy_export_invalid
 
 ```

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

@@ -632,6 +632,25 @@ In some situations a selector may target an element that is not 'visible' to the
 </style>
 ```
 
+### element_implicitly_closed
+
+```
+This element is implicitly closed by the following `%tag%`, which can cause an unexpected DOM structure. Add an explicit `%closing%` to avoid surprises.
+```
+
+In HTML, some elements are implicitly closed by another element. For example, you cannot nest a `<p>` inside another `<p>`:
+
+```html
+<!-- this HTML... -->
+<p><p>hello</p>
+
+<!-- results in this DOM structure -->
+<p></p>
+<p>hello</p>
+```
+
+Similarly, a parent element's closing tag will implicitly close all child elements, even if the `</` was a typo and you meant to create a _new_ element. To avoid ambiguity, it's always a good idea to have an explicit closing tag.
+
 ### element_invalid_self_closing_tag
 
 ```

apps/svelte.dev/content/docs/svelte/98-reference/.generated/shared-errors.md

@@ -1,5 +1,13 @@
 <!-- This file is generated by scripts/process-messages/index.js. Do not edit! -->
 
+### await_outside_boundary
+
+```
+Cannot await outside a `<svelte:boundary>` with a `pending` snippet
+```
+
+TODO
+
 ### invalid_default_snippet
 
 ```

apps/svelte.dev/content/docs/svelte/98-reference/20-svelte.md

@@ -15,6 +15,7 @@ import {
 	createEventDispatcher,
 	createRawSnippet,
 	flushSync,
+	getAbortSignal,
 	getAllContexts,
 	getContext,
 	hasContext,
@@ -23,6 +24,7 @@ import {
 	onDestroy,
 	onMount,
 	setContext,
+	settled,
 	tick,
 	unmount,
 	untrack
@@ -291,6 +293,40 @@ function flushSync<T = void>(fn?: (() => T) | undefined): T;
 
 
 
+## getAbortSignal
+
+Returns an [`AbortSignal`](https://developer.mozilla.org/en-US/docs/Web/API/AbortSignal) that aborts when the current [derived](/docs/svelte/$derived) or [effect](/docs/svelte/$effect) re-runs or is destroyed.
+
+Must be called while a derived or effect is running.
+
+```svelte
+<script>
+	import { getAbortSignal } from 'svelte';
+
+	let { id } = $props();
+
+	async function getData(id) {
+		const response = await fetch(`/items/${id}`, {
+			signal: getAbortSignal()
+		});
+
+		return await response.json();
+	}
+
+	const data = $derived(await getData(id));
+</script>
+```
+
+<div class="ts-block">
+
+```dts
+function getAbortSignal(): AbortSignal;
+```
+
+</div>
+
+
+
 ## getAllContexts
 
 Retrieves the whole context map that belongs to the closest parent component.
@@ -461,6 +497,21 @@ function setContext<T>(key: any, context: T): T;
 
 
 
+## settled
+
+Returns a promise that resolves once any state changes, and asynchronous work resulting from them,
+have resolved and the DOM has been updated
+
+<div class="ts-block">
+
+```dts
+function settled(): Promise<void>;
+```
+
+</div>
+
+
+
 ## tick
 
 Returns a promise that resolves once any pending state changes have been applied.

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

@@ -7,7 +7,7 @@ title: svelte/attachments
 
 ```js
 // @noErrors
-import { createAttachmentKey } from 'svelte/attachments';
+import { createAttachmentKey, fromAction } from 'svelte/attachments';
 ```
 
 ## createAttachmentKey
@@ -48,6 +48,52 @@ function createAttachmentKey(): symbol;
 
 
 
+## fromAction
+
+Converts an [action](/docs/svelte/use) into an [attachment](/docs/svelte/@attach) keeping the same behavior.
+It's useful if you want to start using attachments on components but you have actions provided by a library.
+
+Note that the second argument, if provided, must be a function that _returns_ the argument to the
+action function, not the argument itself.
+
+```svelte
+<!-- with an action -->
+<div use:foo={bar}>...</div>
+
+<!-- with an attachment -->
+<div {@attach fromAction(foo, () => bar)}>...</div>
+```
+
+<div class="ts-block">
+
+```dts
+function fromAction<
+	E extends EventTarget,
+	T extends unknown
+>(
+	action:
+		| Action<E, T>
+		| ((element: E, arg: T) => void | ActionReturn<T>),
+	fn: () => T
+): Attachment<E>;
+```
+
+</div>
+
+<div class="ts-block">
+
+```dts
+function fromAction<E extends EventTarget>(
+	action:
+		| Action<E, void>
+		| ((element: E) => void | ActionReturn<void>)
+): Attachment<E>;
+```
+
+</div>
+
+
+
 ## Attachment
 
 An [attachment](/docs/svelte/@attach) is a function that runs when an element is mounted

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

@@ -1224,6 +1224,32 @@ warningFilter?: (warning: Warning) => boolean;
 A function that gets a `Warning` as an argument and returns a boolean.
 Use this to filter out warnings. Return `true` to keep the warning, `false` to discard it.
 
+</div>
+</div>
+
+<div class="ts-block-property">
+
+```dts
+experimental?: {/*…*/}
+```
+
+<div class="ts-block-property-details">
+
+Experimental options
+
+<div class="ts-block-property-children"><div class="ts-block-property">
+
+```dts
+async?: boolean;
+```
+
+<div class="ts-block-property-details">
+
+Allow `await` keyword in deriveds, template expressions, and the top level of components
+
+</div>
+</div></div>
+
 </div>
 </div></div>
 

apps/svelte.dev/content/docs/svelte/98-reference/30-compiler-errors.md

@@ -485,6 +485,12 @@ Expected token %token%
 Expected whitespace
 ```
 
+### experimental_async
+
+```
+Cannot use `await` in deriveds and template expressions, or at the top level of a component, unless the `experimental.async` compiler option is `true`
+```
+
 ### export_undefined
 
 ```
@@ -539,6 +545,12 @@ The arguments keyword cannot be used within the template or at the top level of
 %message%
 ```
 
+### legacy_await_invalid
+
+```
+Cannot use `await` in deriveds and template expressions, or at the top level of a component, unless in runes mode
+```
+
 ### legacy_export_invalid
 
 ```

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

@@ -653,6 +653,25 @@ In some situations a selector may target an element that is not 'visible' to the
 </style>
 ```
 
+### element_implicitly_closed
+
+```
+This element is implicitly closed by the following `%tag%`, which can cause an unexpected DOM structure. Add an explicit `%closing%` to avoid surprises.
+```
+
+In HTML, some elements are implicitly closed by another element. For example, you cannot nest a `<p>` inside another `<p>`:
+
+```html
+<!-- this HTML... -->
+<p><p>hello</p>
+
+<!-- results in this DOM structure -->
+<p></p>
+<p>hello</p>
+```
+
+Similarly, a parent element's closing tag will implicitly close all child elements, even if the `</` was a typo and you meant to create a _new_ element. To avoid ambiguity, it's always a good idea to have an explicit closing tag.
+
 ### element_invalid_self_closing_tag
 
 ```

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

@@ -184,6 +184,14 @@ Certain methods such as `mount` cannot be invoked while running in a server cont
 
 <!-- This file is generated by scripts/process-messages/index.js. Do not edit! -->
 
+### await_outside_boundary
+
+```
+Cannot await outside a `<svelte:boundary>` with a `pending` snippet
+```
+
+TODO
+
 ### invalid_default_snippet
 
 ```

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

@@ -41,6 +41,22 @@ function add() {
 }
 ```
 
+### await_reactivity_loss
+
+```
+Detected reactivity loss
+```
+
+TODO
+
+### await_waterfall
+
+```
+An async value (%location%) was not read immediately after it resolved. This often indicates an unnecessary waterfall, which can slow down your app.
+```
+
+TODO
+
 ### binding_property_non_reactive
 
 ```