Components / Notification component
gooey-toast
Represent an asynchronous action with a changing toast.
Understand the resource
What it is.
The primary documentation describes morphing React notifications with promise tracking, actions and configurable timing. The published package spelling is goey-toast even though the product heading uses gooey-toast.
When it is useful
A short save or background action needs feedback alongside its persistent state.
A proposed application
Put it to work.
This example illustrates a possible use. The proposed workflow and expected result are separate from the bounded checks recorded below.
Try this
Connect a synthetic save to pending, success and failure messages, with a visible recovery action for errors.
Result to aim for
A notification sequence tied to real operation results.
Before you start
What you need.
- React, react-dom and framer-motion peer dependencies according to the primary documentation.
The practical boundaries
What to watch for.
- A transient toast must not be the only record of a failed or consequential action.
- Test announcements, dismissal, reduced motion and focus; the readable evidence came from the primary page’s indexed documentation, not a runtime run.
Review record
What we could establish.
- The direct public page rendered during this pass. Its Success demo produced notification UI with semantic status nodes. No local package install, real backend action or full accessibility audit was performed.
The source-review notes describe documentation and identity. The account-free evaluation below records exactly which public interaction or local fixture was checked, what happened, and what remains untested.
Check current access, terms, licensing and data handling before using a resource with your own material.
Runtime and security evaluation
What the evaluation covers.
The public Success demo increased semantic notification nodes from two to four and displayed success text. This was a synthetic notification, not a real save or asynchronous backend workflow.
Methods: Public HTTP response · Public browser sample. A completed check covers the stated sample; it is not a safety certification.
- Target
- https://goey-toast.vercel.app/
- Version or capture
- Unversioned public page checked 2026-10-19
- Integrity scope
- sha256:a19f3f88c740372597be59c8fe5b420404082c170a26f97f56054815a44bec5f
Test conditions
- Chromium 155.0.8059.82 on Windows; fresh temporary profile and fresh account-free contexts.
- Public HTTPS GET/HEAD requests only; telemetry/auth routes and WebSockets blocked. No account storage or credential environment variables.
Individual checks and observations
Public document and DOM
passPublic browser sample: Fresh Chromium GET, then inspect rendered controls after hydration delay
Observed: HTTP 200; 70 captured button labels; 6 inputs; 0 canvases.
Success notification display
passPublic browser sample: Trigger Success and observe a rendered live/status notification
Observed: Semantic notification nodes 2 -> 4; success text detected=true.
Security findings and boundaries
Passive inspection of the public response headers, requested hosts and the named browser sample. No active exploitation, authenticated permissions test or complete security audit.
Observed · caution
A toast is not proof that an operation succeeded
The demo produced notification UI without an underlying business action. Connect success and error states to verified application results, and retain important status outside a disappearing toast.
Practical caveats
- Test notification lifetime, keyboard recovery and persistent error handling in the application that will use it.
- Pin and recheck the selected version or sample before adoption; the observations apply only to the scope and date shown.
What remains untested
- No local package install, screen-reader session, promise failure integration or real backend action.
- Fresh-browser restrictions can affect external assets and hydration. Initial failed selectors and limited probes remain in the evidence; they are not blanket product failures.
- Dismissal, auto-expiry and notification lifetime were not exercised; the sample covers display after activating Success.
Security limits
- No authenticated workspace, private content, production backend permissions or data-retention verification.
- No local package install, screen-reader session, promise failure integration or real backend action.
Evaluation sources
Follow the evidence
Sources and further reading.
Keep exploring