Valtio proxy object different, depending on where it is logged

[HenrikZabel]

So I have the following Valtio object:

When I log it in the proxy, I get the following:

<target>: Object { “2024-06-11”: Proxy, “2024-06-12”: Proxy, “2024-06-13”: Proxy, ... }
“2024-06-11”: Proxy { <target>: (2) [...], <handler>: {...} }
“2024-06-12”: Proxy { <target>: [], <handler>: {...} }
“2024-06-13”: Proxy { <target>: [], <handler>: {...} }
“2024-06-14”: Proxy { <target>: [], <handler>: {...} }
“2024-06-15”: Proxy { <target>: [], <handler>: {...} }
“2024-06-16”: Proxy { <target>: [], <handler>: {...} }
<prototype>: Object { ... }
<handler>: Object { deleteProperty: deleteProperty(target, prop), set: set(target, prop, value, receiver) }

If I log it outside, I get the following:

<target>: Object { “2024-06-11”: (2) [...], “2024-06-12”: [], “2024-06-13”: [], ... }
“2024-06-11”: Array [ {...}, {...} ]
“2024-06-12”: Array []
“2024-06-13”: Array []
“2024-06-14”: Array [ { {...} ]
“2024-06-15”: Array []
“2024-06-16”: Array []
<prototype>: Object { ... }
<handler>: Object { get: get(e, n), has: has(t, n), getOwnPropertyDescriptor: getOwnPropertyDescriptor(e, t), ... }

The array stores tasks:

export type Task = {
  id: string;
  created_at: Date;
  title: string;
  note?: string;
  color: “color-1” | “color-2” | “color-3” | “color-4” | “color-5” | “color-6” | “color-7” | “color-8” | “color-9”;
  date: Date;
  subtasks?: string;
  reminder?: Date | null;
  done: boolean;
  position: number;
  user_id: string;
  anchor_id?: UUID | null;
};

I only change the date. Then the above happens. An item disappears at “2024-06-14”. It is certainly not removed anywhere by me. I have checked this several times. If I log JSON.stringify(...) console.log, then I get an item at “2024-06-14” - if I log the proxy directly, then I get that from the top.

Why is there this difference and how can I prevent it from happening?

[0-don]

should be working, strange

[dai-shi]

Can you create a very minimal reproduction?

[HenrikZabel]

I somehow managed to fix it. It seems like this is more a problem of logging the results to the console. I am going to close this discussion.