Svelte 5: Sub-object losing reactivity about svelte HOT 3 CLOSED

This definitely looks like a bug. My hunch — can't check right now — is that it's caused by this effect_active() check:

We should probably just always run this logic, even if we're getting the value in a non-reactive context (i.e. during component init)

from svelte.

#11102 is insufficient — we need to remove the check altogether, not replace it with current_effect !== null

from svelte.

Note that you only have reactivity in App because it's not in runes mode.
REPL with mode set

I think this might be as intended. The proxy is only applied at the root.

Generally when destructuring from something stateful, one should use $derived.

const { settings } = $derived(context);

This then also works for primitives:

const { settings: { showInRgb } } = $derived(context);

REPL

from svelte.