useHydrateAtoms conflicts with useAtomsDebugValue

[yf-yang]

useHydrateAtoms conflicts with useAtomsDebugValue

[dai-shi]

Nice catch.

Hm, I naively thought about delaying like this,

diff --git a/src/vanilla/store.ts b/src/vanilla/store.ts
index fa7e7fb..e84a632 100644
--- a/src/vanilla/store.ts
+++ b/src/vanilla/store.ts
@@ -562,9 +562,11 @@ export const createStore = () => {
     const result = writeAtomState(atom, ...args)
     const flushed = flushPending()
     if (import.meta.env?.MODE !== 'production') {
+      Promise.resolve().then(() => {
         storeListenersRev2.forEach((l) =>
           l({ type: 'write', flushed: flushed as Set<AnyAtom> })
         )
+      })
     }
     return result
   }

but maybe we should do it in useAtomsDebugValue?

[yf-yang]

LGTM, btw is queueMicroTask better?

[dai-shi]

Well, our build still targets IE 11,

jotai/rollup.config.js

Line 96 in 247d9b1

babelPlugin(getBabelOptions({ ie: 11 })),

even though, it may not work perfectly.

queueMicroTaks doesn't seem available: https://caniuse.com/mdn-api_queuemicrotask

but maybe we should do it in useAtomsDebugValue?

I don't think we should add a delay in Jotai, because there are some use cases for sync behavior.
Can you open a PR in jotai-devtools?