Setting nested state make the other states change (their values didn't change)

[khuongtp]

Setting nested state make the other states change (their values didn't change)

Link to reproduction

https://codesandbox.io/p/sandbox/amazing-rhodes-6yp8c5?file=%2Fsrc%2FApp.tsx

Please view the console, you can see that the components that watch count re-render even though count is the same. Refresh the page in code sandbox make it work as expected but on my real machine it doesn't.
Here is my console log no matter how many times I reload the page

(I'm using vite btw)
I did some research and found out that this piece of code was the problem, look at count in the useLayoutEffect dependencies, but I still think it's a bug cause the watched state literally didn't change

const count = useTestStore((state) => {
  return state.count;
});
const setNest1 = useTestStore((state) => {
  return state.setNest1;
});

useLayoutEffect(() => {
  setNest1({ key: "nest2", value: { value1: 1 } });
}, [setNest1, count]);

Check List

Please do not ask questions in issues.

• [ x] I've already opened a discussion before opening this issue, or already discussed in other media.

Please include a minimal reproduction.

• [ x] I've added a link to a typescript playground or codesandbox with a minimal reproduction.

Please check this if you're filing an issue regarding TypeScript.

• [ x] I've read the typescript guide, in particular that create is to be used as create<T>()(...) and not create<T>(...).

[dai-shi]

Isn't it because of useLayoutEffect?
Can you try wrapping console.log with useEffect and see if the result is expected?

useEffect(() => {
  console.log('...');
});

[khuongtp]

Why TestComponent3 gets logged twice when count only changes from undefined to 999, and in the code I already checked if count is undefined then don't log

[dbritto-dev]

@khuongtp that's expected because by default we do shallow comparison

[dbritto-dev]

@khuongtp something to keep in mind if that you are calling a setState function twice at same time on mounting which means that at that point count is undefined in both calls that could lead to two triggers/renders

[dbritto-dev]

so I would say that's the current behavior is right there's no issue here

[dbritto-dev]

btw, here you go -> https://codesandbox.io/p/sandbox/amazing-rhodes-forked-xzrfj2