Untrack on store arrays

Yesterday I had some misunderstandings around

createEffect

createEffect

and stores. Today I probably have similar misunderstandings around

untrack

untrack

.

My assumption was that, e.g.

createEffect(() => {
  const prevArr = untrack(() => prevConfig.arr);
  setPrevConfig("arr", 0, { x: 1 });
});

createEffect(() => {
  const prevArr = untrack(() => prevConfig.arr);
  setPrevConfig("arr", 0, { x: 1 });
});

would not re-trigger the effect. That, however, seems not to be the case. I'm sure there's a good reason for it. It feels quite unintuitive to me though.

https://playground.solidjs.com/anonymous/fbb65302-6799-436c-9abd-287968aaa708

Solid Playground

Quickly discover what the solid compiler will generate from your JSX template

REEEEE•4/21/25, 2:03 AM

The problem is that each property of a store is a signal, so really all you're doing with that untrack is stopping changes to the "arr" signal from triggering the effect but not the properties within "arr" that could also be signals or even the

lemonadOP•4/21/25, 2:15 AM

So there’s no way to untrack arrays in stores? I tried untracking the length and each individual index before reading but that did not help.

webstrand•4/21/25, 2:24 AM

it sounds like you really want instead? To suppress the deep reactivity