fix: toast not appearing when toast.* called from useEffect hook #251
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
## Issue After calling a toast.* function from within a useEffect hook, the toast does not appear (see the new test case in toast.test.tsx for an example). ## Cause The `useStore` hook (used by `Toaster`) calls "useState" to get the current state of the global `memoryState`, and then calls "useEffect" to set up a subscription to the global `memoryState`. The bug is caused when a change to the global `memoryState` happens after "useState" is called, but before the "useEffect" callback is run. This can happen e.g. if we call a toast.* function from within another component's useEffect hook. ## Solution To setup the global `memoryState` subscription, we use the "useLayoutEffect" hook instead. This hook runs the effect synchronously, so no change to the global `memoryState` can happen before the effect is run. ## Alternatives `useSyncExternalStore` is a new hook that is designed to solve this problem and is built into React; we could use this hook instead: https://reactjs.org/docs/hooks-reference.html#usesyncexternalstore
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
-- Issue Calling a toast.* function before rendering the `<Toaster>` component, then rendering the `<Toaster>` component, would cause the toast to not appear or to appear "stacked up" on top of each other. -- Cause The `useStore` hook was using `useState` and `useEffect` to subscribe to the global `memoryState`; unfortunately, in various cases it was possible for change to occur to `memoryState` before the `useEffect` callback was called. Since the `useEffect` callback hadn't run, those changes didn't cause a re-render of the `<Toaster>` component. -- Solution Use the `useSyncExternalStore` hook instead of `useState` and `useEffect`; it handles these cases correctly. I've added a dependency on the `use-sync-external-store` shim so that React version below 18 are still supported. -- Related timolins#253
|
I am also experiencing this bug. toast called inside |
…causing-toast-to-not-appear
|
@timolins Any chance of getting this merged? I just merged |
|
Hey, has anything changed with getting this fixed or merged into main. This problem still seems to be hanging around. Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issues
toast.*function from within a useEffect hook, the toast does not appear (see the new test case in toast.test.tsx for an example).<Toaster>component, then rendering the<Toaster>component, would cause the toast to not appear or to appear "stacked up" on top of each other.Cause
The
useStorehook (used byToaster) calls "useState" to get the current state of the globalmemoryState, and then calls "useEffect" to set up a subscription to the globalmemoryState.The bug is caused when a change to the global
memoryStatehappens after "useState" is called, but before the "useEffect" callback is run. This can happen e.g. if we call a toast.* function from within another component's useEffect hook.Solution
Use the
useSyncExternalStorehook instead ofuseStateanduseEffect; it handles these cases correctly.I've added a dependency on the
use-sync-external-storeshim so that React version below 18 are still supported.Related Github issues
#101
#57
#142
#253