Runtime warnings

Using `bind:value` together with a checkbox input is not allowed. Use `bind:checked` instead

Component %component% has an export named `%key%` that a consumer component is trying to access using `bind:%key%`, which is disallowed. Instead, use `bind:this` (e.g. `<%name% bind:this={component} />`) and then access the property on the bound component instance (e.g. `component.%key%`)

A component is attempting to bind to a non-bindable property `%key%` belonging to %component% (i.e. `<%name% bind:%key%={...}>`). To mark a property as bindable: `let { %key% = $bindable() } = $props()`

%parent% called `%method%` on an instance of %component%, which is no longer valid in Svelte 5. See https://svelte-5-preview.vercel.app/docs/breaking-changes#components-are-no-longer-classes for more information

Attempted to instantiate %component% with `new %name%`, which is no longer valid in Svelte 5. If this component is not under your control, set the `compatibility.componentApi` compiler option to `4` to keep it working. See https://svelte-5-preview.vercel.app/docs/breaking-changes#components-are-no-longer-classes for more information

A derived value cannot reference itself recursively

Keyed each block has duplicate key at indexes %a% and %b%

Keyed each block has duplicate key `%value%` at indexes %a% and %b%

`%rune%` cannot be used inside an effect cleanup function

Effect cannot be created inside a `$derived` value that was not itself created inside an effect

`%rune%` can only be used inside an effect (e.g. during component initialisation)

Maximum update depth exceeded. This can happen when a reactive block or effect repeatedly sets a new value. Svelte limits the number of nested updates to prevent infinite loops

Failed to hydrate the application

Could not `{@render}` snippet due to the expression being `null` or `undefined`. Consider using optional chaining `{@render snippet?.()}`

`%name%(...)` cannot be used in runes mode

Cannot do `bind:%key%={undefined}` when `%key%` has a fallback value

Rest element properties of `$props()` such as `%property%` are readonly

The `%rune%` rune is only available inside `.svelte` and `.svelte.js/ts` files

Property descriptors defined on `$state` objects must contain `value` and always be `enumerable`, `configurable` and `writable`.

Cannot set prototype of `$state` object

Reading state that was created inside the same derived is forbidden. Consider using `untrack` to read locally created state

Updating state inside a derived or a template expression is forbidden. If the value should not be reactive, declare it without `$state`

Cannot use `{@render children(...)}` if the parent component uses `let:` directives. Consider using a named snippet instead

`%name%(...)` can only be used during component initialisation

`%name%` is not a store with a `subscribe` method

The `this` prop on `<svelte:element>` must be a string, if defined