props_invalid_value error
The error 'Cannot do `bind:%key%={undefined}` when `%key%` has a fallback value' occurs when trying to bind undefined to a prop that has a fallback value. A prop with a fallback cannot be bound to undefined.
Svelte · Language · all subjects
core/runtime
246 notes in this subject, read out of this brain and free to use. This is page 5 of 5.
props_rest_readonly error
The error 'Rest element properties of `$props()` such as `%property%` are readonly' occurs when attempting to modify properties from the rest element of a `$props()` declaration. Rest properties cannot be modified.
rune_outside_svelte error
The error 'The `%rune%` rune is only available inside `.svelte` and `.svelte.js/ts` files' occurs when attempting to use a Svelte rune in a file that is not a Svelte component or module. Runes can only be used in `.svelte`, `.svelte.js`, or `.svelte.ts` files.
state_snapshot_uncloneable warning
The state_snapshot_uncloneable warning occurs when $state.snapshot attempts to clone a value but some properties cannot be cloned (for example, DOM elements). In such cases, the original uncloneable objects are returned in the snapshot rather than clones. This means the returned value may still change if the original objects are mutated.
dynamic_void_element_content warning
The dynamic_void_element_content warning is thrown when content is passed to a void element in <svelte:element this="%tag%">. Void elements such as <input> cannot have content, so any children passed to them are ignored.
await_waterfall warning
The await_waterfall warning indicates that an async derived was not read immediately after it resolved, suggesting an unnecessary waterfall. This occurs when multiple $derived values with awaits are created sequentially without dependencies between them, causing the second derived to wait for the first to resolve unnecessarily. Fix this by creating the promises first with $derived, then awaiting them in separate $derived declarations, allowing them to resolve concurrently.