Toaster styles lost? #502
Replies: 1 comment
-
The top level You'll want to make sure to have more error boundaries throughout the routes so you can avoid errors bubbling up to the top. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, I've adopted the Epic Stack's approach for toast messages but I've run into a problem. When a user triggers an error boundary the Toaster's styles are ejected from the document head. One workaround would be download the current version of the CSS and import that into the component, but obviously that isn't ideal.
Is there a fix in the Epic Stack for this already and I've missed it? If not, can anyone think of a decent way of solving the issue?
Thanks
Tom
Beta Was this translation helpful? Give feedback.
All reactions