Feat: expose toast.subscribe for subscribing to toast lifecycle outside React - #776
Open
nbarinov wants to merge 2 commits into
Open
Feat: expose toast.subscribe for subscribing to toast lifecycle outside React#776nbarinov wants to merge 2 commits into
toast.subscribe for subscribing to toast lifecycle outside React#776nbarinov wants to merge 2 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
nbarinov
force-pushed
the
feat/toast-subscribe
branch
from
August 11, 2026 13:08
94d4b57 to
ff3e94a
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
toastalready exposesgetToasts()/getHistory(), but the only way to react to changes is the React-onlyuseSonner. This exposes the existing internalToastState.subscribeastoast.subscribe(cb), returning an unsubscribe function – symmetrical to the getters, zero new logic.Use case: we render a floating checkout pill that must yield to any visible toast ("only one hanging element"). The visibility signal lives in a framework-agnostic store outside the React tree, and today the only way to feed it is a probe component with
useSonnermounted next to<Toaster />.Withtoast.subscribethe store subscribes directly.Added an e2e test covering add + dismiss events and unsubscribe semantics.