7nik

This is the same as https://github.com/sveltejs/svelte/issues/9948 but about Svetle 4

No, it doesn't. When a variable changes (marked dirty), the following happens: 1. looping over each `$:` block and running the ones that depend on dirtied variables; 2. running `beforeUpdate`;...

I thought about infinite loops cause by self-triggering `$effect` and came to idea that if your logic cause infinite loops then the logic is wrong and it needs some loop...

`bind:this` on a component will "return" a component instance but not a DOM element! `ref` is `undefined` because your components have no properties on instance - you can define them...

Component API is changed in Svelte 5. You can read a bit in #9827. Also, there is no `get_current_component()` anymore (see #9189), and I don't see an alternative. It was...

It was intentionally introduced in #9764

Those examples with auto-configuration feel too magic. E.g. when I see the following code: ```js let myState = $state({ buffer: new Int32Array() }); ``` I'll ask myself: is `myState.buffer` reactive?...

Let's look at this example: ```js let myState = $state( {}, { addReactivity: [ "Set"] } ); const set = get_builtin_set(); myState.set = set; ``` Here, `set` is pure build-in...

@vexkiddy seems to be working on the latest version. [REPL](https://svelte-5-preview.vercel.app/#H4sIAAAAAAAAA0WOwQrCMBBEf2XJpQrV3msseBB_wJv1kKZbDDabkN0WpPTfbangbd7AG2ZSneuRVfmYFBmPqlSXGFWu5BNX4BF7wYU5DMmujWabXJSqplqcjyEJTHAPhgVTDrIGmKFLwUO22QcORJiyU026-NukfxYUC-pmEAkEgUrbO_s-T7s9nKtt8MiDtci8y64jksDLMDSIBDahEWyz_Vzd3IjgEcym6GIbrJbvPrSuc9iqUtKA83P-AmHp8TD2AAAA). Version next.55 is really ancient.

But there are no elements to refer to as `:scope` during compile time. Theoretically, `*:not(* *)` should select only top-level components but it gets compiled into `.svelte-103htr2:not(* *)` so it...