7nik
7nik
The workaround seems to reactify the searched value: the $state never creates wrappers (not sure how reliable this behaviour is). Basically: ```js const value = {}; $state(value) === $state(value); //...
[TS: am I joke for you?](https://www.typescriptlang.org/play/?#code/C4TwDgpgBACghgJzgWwM5QLxQN4CgoFQD0AVCfoVCVAAIAmEYCEAxnMBHVALRQCuqaAAMmAezAAmIVACWAO1Qc4dCoRJFVUMWACMAfgBcUAEajRAGwhw5AGk3aJhqIoTyA5ncozUAJQgBHPhlmOiMXdzsAX1xcADM+ORZgGVE5KABhUWQwVIg5YCgACjBEFFQjeCQ0AEocaNxM7Nz8wuwtBHEdI2AEPmhI6oBuIA) > ```svelte > > ``` What does it even mean? Unacceptable value of `format`? Use type like `"big" | "medium" | "small"`. > `FancyList`...
> Validating the format with code will allow to detect problems during compilation. And it won't work with variables. If the lib authors care, they can do ```js if (!isValid(propX))...
I believe it's a duplicate of #7913 and non-fixable in Svelte 3/4.
Why do you need it when you, in general, control the content of non-contenteditable elements?
any ETA? It breaks auto-builds and annoys to do force installs of libs due to this issue. @Anidetrix are you even OK?
> Experiencing this issue as well, the repro looks like this, though I don't think the playground shows those kinds of link warnings (or does it?): https://svelte-5-preview.vercel.app/#H4sIAAAAAAAAE0VPTWvDMAz9K0Ls0LJAumuaFHbYP9itGTRxlEbMkUMsrwzj_z6cQHfU-9J7EUe25LG6RpRuJqzwfVmwQP1d8uF_yCphgd6F1WSk9mblRS-ttGpJwbggCg28eO2UDqfjuZXMjUGMshNgMSvNJHo4QsxMq7vntYG3LNa0O3Jar_Jhz1CW8DmxB8tCcCf1oBPBo1uF5Q5DIFC3QbeeZah0Yn-Dnqx7tFKX_w2l7oOqE3BiLJvvJj7bJHham7i9TdumTecriFvJlPP2jAsWOLuBR6YBK10Dpa_0B4kJDiNAAQAA > > Anyway,...
@theetrain, how can it be a breaking change if it never worked in Svelte 4? Though it can listed in the new Svelte 5 features. @FoHoOV, this thread is about...
@Facius use [on](https://svelte-5-preview.vercel.app/docs/imports#svelte-events) instead of `node.addEventListener`.
> I'd be happy if _any_ of the following resulted with ` > * `$effect.pre(()=>{if(document?.documentElement) document.documentElement.dataset.theme=pageTheme});` > > * `` > > * `` Obviously, the first option can work...