Antoine Lethimonnier

Looks like this should be opened in https://github.com/sveltejs/svelte.dev/issues instead

@7nik yes indeed, makes sense! I'm quite new to using runes, so I kind of forgot about stores as I was focused on playing around with runes, but yeah, that...

> BTW, due to this, your REPL is considered to be in legacy mode. What does that mean? > * Forbidding variables with the same names as runes would make...

> Svelte 4 / non-rune mode. Weird, it was in Svelte 5 when I posted it. Fixed.

The current warning implies overriding runes is allowed, not that such a thing is not possible and the variable should be renamed

@Conduitry I agree with Simon: my request was to better handle/warn about using "rune-named" variables, whereas the other issue is about allowing `$`-prefixed variables (which I didn't know was not...

`$store` looks great, but adding a rune that will ultimately need to be removed in the next few major versions instead of getting rid of stores altogether doesn't sound like...

Not yet, but they'll very likely get sunset in the next majors

Update: [I made it](https://github.com/WarningImHack3r/vite-plugin-lucide-preprocess) (I still think having it built-in would be better)