-
### Describe the bug
Svelte 5 preview ships with the new create app cli as an option. When using the previous the app cannot compile due to the errors below:
```
VITE v5.0.9 ready in 866 ms
…
-
### Describe the bug
Page store attempting to interface store with svelte5 signels state doesn't work. Looking for how this could be done or if page store should be updated to signels state?
###…
-
### Current Behavior
when created new project with `pnpm create skeleton-app@latest my-skeleton-app` and upgraded svelte to `"svelte": "next"` I am getting this error when I access page
```
…
-
### Describe the problem
When transpiled Svelte code is instrumented with `istanbul`, there are a lot of unrelated statements and branches in the coverage report. The source maps received from `sve…
-
### Describe the problem
The "update" method of **{#each}** blocks is not optimized for immutable object.
When updating a single element of the array, all the elements of the array are reinterpret…
-
### Describe the bug
Snippet with children props does not work on vite dev server.
It works on Svelte 5 repl and building phase on vite project.
So it might be the vite problem
### Repro…
-
### Describe the problem
In svelte5 lets say we have a state that has a primitive value like this `let primitiveState = $state("some value");`. Then we try to listen to its changes with an $effect:…
-
### Current Behavior
I implement forms exactly as they are shown in the website and get the following error:
`Form data sent directly to superForm instead of through superValidate. No initial data…
-
### Describe the bug
Once I upgraded to svelte 5 preview I became unable to compile and run my website due to compile errors. They all seem to stem from the same issue and it's blocking adoptions.
…
-
### Describe the bug
Non backwards-compatible Runes mode can be enabled via `compilerOptions` in `svelte.config.js`
https://svelte-5-preview.vercel.app/docs/runes#how-to-opt-in
```js
export defa…