From c70067542060cb024c1beaaeecec62aba440c87a Mon Sep 17 00:00:00 2001
From: GitHub Actions Bot <github-actions[bot]@users.noreply.github.com>
Date: Thu, 22 May 2025 23:04:45 +0000
Subject: [PATCH] sync docs

---
 .../svelte/03-template-syntax/09-@attach.md   |  4 ++
 .../.generated/client-warnings.md             | 13 +++++
 .../98-reference/.generated/compile-errors.md |  6 ---
 .../.generated/compile-warnings.md            | 19 ++++++++
 .../98-reference/21-svelte-attachments.md     | 48 ++++++++++++++++++-
 .../svelte/98-reference/30-compiler-errors.md |  6 ---
 .../98-reference/30-compiler-warnings.md      | 19 ++++++++
 .../98-reference/30-runtime-warnings.md       | 13 +++++
 8 files changed, 115 insertions(+), 13 deletions(-)

diff --git a/apps/svelte.dev/content/docs/svelte/03-template-syntax/09-@attach.md b/apps/svelte.dev/content/docs/svelte/03-template-syntax/09-@attach.md
index f342945a8a..47939d6375 100644
--- a/apps/svelte.dev/content/docs/svelte/03-template-syntax/09-@attach.md
+++ b/apps/svelte.dev/content/docs/svelte/03-template-syntax/09-@attach.md
@@ -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.
diff --git a/apps/svelte.dev/content/docs/svelte/98-reference/.generated/client-warnings.md b/apps/svelte.dev/content/docs/svelte/98-reference/.generated/client-warnings.md
index 77d1df4cdd..fe90b0db38 100644
--- a/apps/svelte.dev/content/docs/svelte/98-reference/.generated/client-warnings.md
+++ b/apps/svelte.dev/content/docs/svelte/98-reference/.generated/client-warnings.md
@@ -200,6 +200,19 @@ Consider the following code:
 
 To fix it, either create callback props to communicate changes, or mark `person` as [`$bindable`]($bindable).
 
+### select_multiple_invalid_value
+
+```
+The `value` property of a `<select multiple>` element should be an array, but it received a non-array value. The selection will be kept as is.
+```
+
+When using `<select multiple value={...}>`, Svelte will mark all selected `<option>` elements as selected by iterating over the array passed to `value`. If `value` is not an array, Svelte will emit this warning and keep the selected options as they are.
+
+To silence the warning, ensure that `value`:
+
+- is an array for an explicit selection
+- is `null` or `undefined` to keep the selection as is
+
 ### state_proxy_equality_mismatch
 
 ```
diff --git a/apps/svelte.dev/content/docs/svelte/98-reference/.generated/compile-errors.md b/apps/svelte.dev/content/docs/svelte/98-reference/.generated/compile-errors.md
index db848a0299..76ad8de7fb 100644
--- a/apps/svelte.dev/content/docs/svelte/98-reference/.generated/compile-errors.md
+++ b/apps/svelte.dev/content/docs/svelte/98-reference/.generated/compile-errors.md
@@ -1082,12 +1082,6 @@ Expected a valid element or component name. Components must have a valid variabl
 A `<textarea>` can have either a value attribute or (equivalently) child content, but not both
 ```
 
-### title_illegal_attribute
-
-```
-`<title>` cannot have attributes nor directives
-```
-
 ### title_invalid_content
 
 ```
diff --git a/apps/svelte.dev/content/docs/svelte/98-reference/.generated/compile-warnings.md b/apps/svelte.dev/content/docs/svelte/98-reference/.generated/compile-warnings.md
index 7069f90206..b579d38602 100644
--- a/apps/svelte.dev/content/docs/svelte/98-reference/.generated/compile-warnings.md
+++ b/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
 
 ```
diff --git a/apps/svelte.dev/content/docs/svelte/98-reference/21-svelte-attachments.md b/apps/svelte.dev/content/docs/svelte/98-reference/21-svelte-attachments.md
index 68fae2cb1b..497ae3a329 100644
--- a/apps/svelte.dev/content/docs/svelte/98-reference/21-svelte-attachments.md
+++ b/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
diff --git a/apps/svelte.dev/content/docs/svelte/98-reference/30-compiler-errors.md b/apps/svelte.dev/content/docs/svelte/98-reference/30-compiler-errors.md
index 143137c77e..3c748fd79e 100644
--- a/apps/svelte.dev/content/docs/svelte/98-reference/30-compiler-errors.md
+++ b/apps/svelte.dev/content/docs/svelte/98-reference/30-compiler-errors.md
@@ -1087,12 +1087,6 @@ Expected a valid element or component name. Components must have a valid variabl
 A `<textarea>` can have either a value attribute or (equivalently) child content, but not both
 ```
 
-### title_illegal_attribute
-
-```
-`<title>` cannot have attributes nor directives
-```
-
 ### title_invalid_content
 
 ```
diff --git a/apps/svelte.dev/content/docs/svelte/98-reference/30-compiler-warnings.md b/apps/svelte.dev/content/docs/svelte/98-reference/30-compiler-warnings.md
index 6314ffd30d..0e18ba7d43 100644
--- a/apps/svelte.dev/content/docs/svelte/98-reference/30-compiler-warnings.md
+++ b/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
 
 ```
diff --git a/apps/svelte.dev/content/docs/svelte/98-reference/30-runtime-warnings.md b/apps/svelte.dev/content/docs/svelte/98-reference/30-runtime-warnings.md
index 8554eb52d5..5a0b6b9488 100644
--- a/apps/svelte.dev/content/docs/svelte/98-reference/30-runtime-warnings.md
+++ b/apps/svelte.dev/content/docs/svelte/98-reference/30-runtime-warnings.md
@@ -207,6 +207,19 @@ Consider the following code:
 
 To fix it, either create callback props to communicate changes, or mark `person` as [`$bindable`]($bindable).
 
+### select_multiple_invalid_value
+
+```
+The `value` property of a `<select multiple>` element should be an array, but it received a non-array value. The selection will be kept as is.
+```
+
+When using `<select multiple value={...}>`, Svelte will mark all selected `<option>` elements as selected by iterating over the array passed to `value`. If `value` is not an array, Svelte will emit this warning and keep the selected options as they are.
+
+To silence the warning, ensure that `value`:
+
+- is an array for an explicit selection
+- is `null` or `undefined` to keep the selection as is
+
 ### state_proxy_equality_mismatch
 
 ```