I suspect it's because React Query uses useSyncExternalStore. Does that mean it's incompatible with Actions?
codesandbox.io/p/sandbox/re...
cc @tkdodo.eu @ricky.fm
I suspect it's because React Query uses useSyncExternalStore. Does that mean it's incompatible with Actions?
codesandbox.io/p/sandbox/re...
cc @tkdodo.eu @ricky.fm
(Screenshot shows both the first and second renders using "time slicing".)
Downside is you can no longer use it as a hook. 🤔
(Screenshot shows both the first and second renders using "time slicing".)
Downside is you can no longer use it as a hook. 🤔
#1 uses useSyncExternalStore. The hydration render (isClient: false) is "time sliced" but the subsequent render (isClient: true) is not "time sliced". ❌
#2 uses useState + useEffect. Both renders are time sliced. ✅
codesandbox.io/p/devbox/rea...
#1 uses useSyncExternalStore. The hydration render (isClient: false) is "time sliced" but the subsequent render (isClient: true) is not "time sliced". ❌
#2 uses useState + useEffect. Both renders are time sliced. ✅
codesandbox.io/p/devbox/rea...
Store: chromewebstore.google.com/detail/custo...
Code: github.com/OliverJAsh/c...
(There are lots of existing extensions for this but they're all bloatware. Also shocked this still isn't built-in to dev tools…)
Store: chromewebstore.google.com/detail/custo...
Code: github.com/OliverJAsh/c...
(There are lots of existing extensions for this but they're all bloatware. Also shocked this still isn't built-in to dev tools…)
Turns out it was because of this: ishadeed.com/article/css-...
I wonder if dev tools could make this clearer? cc
@bram.us @nerdy.dev @una.im
Turns out it was because of this: ishadeed.com/article/css-...
I wonder if dev tools could make this clearer? cc
@bram.us @nerdy.dev @una.im