Dominic Gannaway

We decided that this is most definitely going to be a breaking change so it will have to wait for Svelte 6. In the mean time, I've tried to alleviate...

There is already a warning for this problem, as you can see in the REPL.

> The current warning implies overriding runes is allowed, not that such a thing is not possible and the variable should be renamed I didn't interpret the warning to imply...

Whilst this is super interesting, this isn't a route we plan on taking in the future. Given how stale and conflicted this PR is, I'm closing for now.

@ottomated oxc looks promising but its very early days there still, and the change in AST format would be a huge change for us, so likely something for the far...

Is this Svelte 4 or Svelte 5?

There's a couple of things here that don't seem right. Trying to convert a store 1:1 with runes isn't the right approach here. Firstly, you can still use stores here...

> Hey, @trueadm I have a question for you regarding $effect.root and its cleanup. > > Is the cleanup necessary even if the effects inside the root effect require no...

> Interesting. I ask because I have been freely creating Svelte v5 stores using `$effect.root()` in the constructor of a base class without a single worry in my head. Is...

@paoloricciuti I'm struggling with this one because of the tests you added in https://github.com/sveltejs/svelte/pull/11720. Specifically, this line doesn't seem right: https://github.com/sveltejs/svelte/blob/main/packages/svelte/src/internal/client/dom/elements/attributes.js#L58 If I change it to: ```js if (attributes.value ===...