Mathias Picker

> This is working as intended...you should update state from the template. Thanks for reporting tho. What does `update state from the template` mean?

> [Something like this](https://svelte.dev/playground/hello-world?version=5.0.5#H4sIAAAAAAAACm3KTQrCMBRF4a2EiwOF4s80VsF1GAexPKEQn6Hvtighe5cKOnJ4Pk7BrU9i8OcCvrLAfwANNN7nOuW8tkkSZ7tGk3_ePZSiNHi01g195jGoc0nopphGcQe3MEbKcrvaB203vylo-R67igaUJ-E5jFIv9Q3LBLLRnQAAAA==): > > ```svelte > > let value = $state(0); > > > {value = 1} > ``` > > The template (HTML part of the component)...

I'm having the same problem in a component with bindable properties. If i set `const { ... } = $props()` then my code triggers a `Cannot assign to X because...

> I'm in the same boat as @MathiasWP . Upgrading my app to Svelte 5. In most places, I use const for my $props without issue. But if it includes...

> Would probably need more details of which route the issue was reported for and the page options affecting that (prerendered, ssr, etc) > > I can only imagine this...

> > The only page option we have defined is `export const ssr = true`. > > SSR is true by default for SvelteKit, so it's likely there is a...

Got another error with `Cannot read properties of undefined (reading 'universal')` in Sentry, but this one had some more stack-traces:

I managed to get access to our old Sentry with the `Failed to fetch dynamically imported module` error, but there's not a lot information in our Sentry dashboard on this...

Any status on this issue? We're getting this error at least once a day

What is your suggested solution to solve this @eltigerchino? If we remove this we will encounter the error mentioned in #9089 again, which is a real issue for us (we...