1 Commits (4d5139552dac8593c5e020846fa7ce8e96ea97b7)

Author	SHA1	Message	Date
Kamil Jakubus	38ef714f1a	fix: scope SSR boundary failed snippets to their boundary (#18593) ... Each `<svelte:boundary>` with: ```svelte {#snippet failed(error)} ... {/snippet} ``` generated a function named failed. Sibling boundaries placed both functions in the same SSR scope: ```js { function failed() {} function failed() {} // Identifier `failed` has already been declared } ``` Resulting in a `[PARSE_ERROR] Identifier `failed` has already been declared` error during build time. A let declaration such as `{const x = 0}` can create a nested lexical block, exposing the collision. The fix gives each boundary its own scope: ```js { function failed() {} $$renderer.boundary({ failed }, ...); } { function failed() {} $$renderer.boundary({ failed }, ...); } ``	1 week ago