sveltejs/svelte

Recorded claims

No decisions have been organised from this repository’s history yet — these are individual claims lema extracted, each linked to the discussion it came from.

• Keeping comment-based hydration markers and stripping them in a specific 'DevTools clean mode' was considered and rejected.mined candidatediscussion · 2026-06-07 ↗
• Accepting the DOM pollution caused by comment-based hydration markers was considered and rejected.mined candidatediscussion · 2026-06-07 ↗
• The assertion that dialogs absolutely should have an element with `autofocus` is not entirely accurate, as dialogs automatically focus the first interactive element.mined candidatediscussion · 2026-04-08 ↗
• The Svelte compiler's `autofocus` warning should be removed.mined candidatediscussion · 2026-04-07 ↗
• The internal Svelte logic for `autofocus` should be deprecated and removed in Svelte 6.mined candidatediscussion · 2026-04-07 ↗
• Enabling `unsafe-inline` for Content Security Policy (CSP) is often forbidden.mined candidatediscussion · 2026-03-06 ↗
• Fragile workarounds like patching compiled output, writing build transforms, or monkey-patching `document.createElement` are not robust solutions for Content Security Policy (CSP) nonce injection.mined candidatediscussion · 2026-03-06 ↗
• The claim that using `{@const result = await promise}` inside `<svelte:boundary>` generates "dirty markup" is incorrect.mined candidatediscussion · 2026-04-20 ↗
• Using `{result = await promise}` inside `<svelte:boundary>` to make the result available in the `<script>` tag is not ideal because it introduces unnecessary HTML markup.mined candidatediscussion · 2026-02-16 ↗
• Using dynamic imports with `?enhanced` queries and `$lib` aliases for `enhanced:img` was found problematic due to Vite's limitations.mined candidatediscussion · 2026-01-24 ↗
• The `run` function is not suitable for server-side reactivity because it does not allow updates multiple times.mined candidatediscussion · 2025-12-22 ↗
• Adding an `$effect` rune to the server would be inconsistent because components would maintain reactivity in effects but not in the template.mined candidatediscussion · 2025-12-22 ↗
• The `$derived({value})` approach is not reactive when scalar state is passed to a component.mined candidatediscussion · 2025-12-21 ↗
• Introducing a new rune for creating state with an object argument is not considered a significant improvement.mined candidatediscussion · 2025-12-21 ↗
• Breaking large components into smaller ones is considered an unnecessary and complicated workaround for the problem of state declaration separation.mined candidatediscussion · 2025-12-18 ↗
• Using snippets for local state is considered an unnecessary and complicated workaround for the problem of state declaration separation.mined candidatediscussion · 2025-12-18 ↗
• Using IDE split panes is considered an unnecessary and complicated workaround for the problem of state declaration separation.mined candidatediscussion · 2025-12-18 ↗
• The proposal for advanced component and snippet behavior will likely not be implemented for the time being.mined candidatediscussion · 2026-03-17 ↗
• A user rejected adding scripts to the Chrome DevTools ignore list one at a time for Svelte 5 debugging due to the large number of scripts.mined candidatediscussion · 2025-11-11 ↗
• Using a custom `accessors` helper function to manage `$state()` variables in an object literal is not effective because the Svelte compiler still wraps the variables in `$.get()`.mined candidatediscussion · 2025-09-18 ↗