If you could fix ONE thing about your current Toast library, what would it be? 🤔 #195333
-
Discussion TypeQuestion Discussion ContentHey everyone! We all use them: If you had a magic wand and could fix exactly one problem or annoyance with the toast library you are currently using in your project, what would it be? (Dealing with z-indexes? Nightmare to style? Impossible to trigger from outside components? Let me know!) |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
One thing I’d fix instantly: global control outside React components. A lot of toast libraries still feel too tightly coupled to component trees, which becomes annoying in real apps where you want to trigger notifications from API layers, Zustand stores, websocket handlers, auth interceptors, or server actions cleanly. Second would probably be z-index and stacking issues inside modals/drawers. That problem still shows up way too often for something every app uses. |
Beta Was this translation helpful? Give feedback.
-
|
100% agree with both of these! Triggering a toast from a generic utility file shouldn't feel like you're fighting the framework's architecture. The z-index/modal stacking issue is definitely a classic frontend struggle that never seems to fully go away, no matter the library. Have you found any specific toast library (like |
Beta Was this translation helpful? Give feedback.
-
|
One thing I’d fix is making toasts easier to trigger globally without weird workarounds or tight coupling to components. In larger apps, especially with async actions, auth flows, API interceptors, or server actions, I often want to trigger a toast from anywhere cleanly. Some libraries make this smooth, others start feeling messy fast. Second biggest annoyance: styling consistency. Getting toasts to perfectly match a custom design system/theme sometimes becomes harder than it should be, especially with dark mode and Tailwind-heavy projects. Also z-index battles with modals and drawers deserve their own horror movie 😭 |
Beta Was this translation helpful? Give feedback.
One thing I’d fix instantly: global control outside React components.
A lot of toast libraries still feel too tightly coupled to component trees, which becomes annoying in real apps where you want to trigger notifications from API layers, Zustand stores, websocket handlers, auth interceptors, or server actions cleanly.
Second would probably be z-index and stacking issues inside modals/drawers. That problem still shows up way too often for something every app uses.