Status & Feedback
Sonner
Sonner provides toast-like notifications with imperative helpers. Explain what is happening, what changed and what someone can do next. Pair visual status with language that still makes sense without its color. Import it from @/components/kamod-ui/sonner.
Source · Design reference · API reference · Theming · Styles
Interactive preview
Preact example Local preview theme · Responsive styles follow the preview widthFull widthInstallation
Import Sonner and helper functions from @/components/kamod-ui/sonner.
pnpm add @kamod-ch/uiCopy an example with @kamod-ch/ui or the matching @kamod-ch/ui/… subpath. The code block switches between those two installs. Connect The Global Theme CSS and Tailwind Source Detection before your first render.
Usage
Mount Sonner once near app root, then trigger notifications from events.
import { Sonner } from "@kamod-ch/ui";Choose a complete composition from the examples below; required child components and props vary by pattern.
Component Examples & Variants
Explore Sonner in Different Contexts, from the starting pattern to the compositions below. Begin with Basic Toast, then compare the examples that match your content, state and layout. These are working patterns to adapt, not a list of interchangeable variant values: check the API Reference before using a prop or combining behaviors. Look at the surrounding labels, supporting text and spacing as well as the component itself.
Read the Result and Its Implementation Together. Use each showcase’s Code view to inspect imports and composition, or its Prompt view to prepare a setup or adaptation brief. Try the narrow preview and local theme controls before connecting real data, and use Reset to return an example to its initial state. Keep layout changes in class utilities where appropriate; follow the Component Styles Guide for hierarchy and the Theming Guide for shared surfaces and colors. The Accessibility Notes explain what to preserve when making those changes.
Basic Toast
Confirm the Outcome of an Action. Trigger a short success notification after an operation has actually completed. The toast summarizes the result near the edge of the interface, while the main screen should also reflect the updated application state.
Keep the message specific, mount the notification surface once in the application and provide persistent feedback elsewhere when the result is too important to disappear automatically.
Dismissible Toast
Track the Notification that Belongs to the Workflow. Retain the notification identifier when a later workflow change needs to dismiss the toast programmatically. This ties the message's lifetime to the operation it describes rather than leaving outdated feedback visible after the context changes.
Keep the returned identifier with the relevant task and avoid dismissing unrelated messages; a notification disappearing should not be mistaken for proof that the operation succeeded.
Interactive preview
Preact example Local preview theme · Responsive styles follow the preview widthFull widthProps and Data
Configure Sonner using the contracts below. Read the documented options alongside the Source Definitions to understand which values your application supplies and which details the component owns. Start with a prop or helper, then follow its type link to inspect the declaration without leaving the page.
Props, slots and variants for this component.
Type cards are extracted from this checkout’s TypeScript source at build time. Props inherited through HTMLAttributes, Omit or variant helpers remain references in those declarations; their fields are not flattened here. Match the reference to your installed version, and check a package’s exports before writing an import type. A type exported by a source file is not necessarily re-exported by @kamod-ch/ui.
Component Props
? means a field can be omitted; it does not promise a fallback value. Existing documented defaults remain alongside the descriptions. For callbacks, check the argument and return types before connecting your own state or services.Data Type Reference
Expand a card to inspect and copy the exact declaration. The code header identifies its repository file; follow imported or inherited types in the Implementation Source when you need the complete dependency chain. Required-field summaries cover fields declared directly in that type. Source-only helpers and inferred schema outputs describe the local implementation, not additional props you can pass to every component.
SonnerToast
3 declared fieldsSonnerToastsonner-store.ts. Referenced types retain their original names; inspect that file for imports and supporting definitions. Inspect the Complete Definition of SonnerToast before adapting it.id, titleAccessibility
Build the Complete Interaction, Including the Parts Outside Sonner. The notes below distinguish the current implementation from the labels, content and behavior your application supplies. Start with the Live Preview, check the Props and Data Reference, and test the finished composition with real content rather than assuming that an unchanged visual example covers every use case.
Built-in Behavior and Defaults
The current Sonner renderer displays stacked messages and a native Dismiss button. It does not add a live-region role or aria-live attribute. Do not assume another library's Sonner announcement behavior is present in this implementation.
Labels and Relationships
Use clear titles and descriptions naming the affected operation. If several messages are visible, the repeated Dismiss buttons need enough context to identify which message they close; inspect and improve that relationship in the rendered UI.
Keyboard and Focus
Keyboard users can reach the native dismiss action, but arrival of a message is not automatically announced. Supply an appropriate persistent status mechanism in your application or extend the renderer before relying on it for important asynchronous feedback.
States and Integration Details
Do not make a toast the only evidence that saving failed. Keep field or request errors in the relevant page content, avoid moving focus to every new message, and ensure messages do not cover essential controls at narrow widths.
Verify the Complete Interaction
Check Behavior as Well as Markup. Work through these scenarios in the application where the component will be used. Automated checks can help find structural problems; also review the reading experience with a screen reader, keyboard focus and the actual feedback from your application.
- Trigger a message with a screen reader and verify your chosen status mechanism actually announces it.
- Dismiss one of several messages using the keyboard without confusing their targets.
- Test a failed request with the toast closed and confirm the error and recovery action still exist.
Recheck the result after changing Theme Tokens, translations or class overrides. Include text enlargement, narrow layouts and reduced-motion settings where animation is present. Inspect the Component Source when a behavior differs from your expectation; a role or state attribute does not implement keyboard interaction by itself.
For background, read the WAI-ARIA Authoring Guidance and Keyboard Interface Guidance. These explain the patterns; verify browser and assistive-technology behavior for the implementation and audience you actually support.
You have the pieces. Put them into one real interaction, keep its state in one place, and check the result with the content your application will actually show.
Connect the Foundation
Return to Choose and Compose Components to connect this reference to a working screen. Keep global CSS in one entrypoint and import only the components that screen needs.
Build the Surrounding Screen
Find a neighboring interaction in the Component Library, or start with a complete Block. Replace sample content and destinations before refining the layout; a local class change can stay with the composition.
Make the Result Hold Up
Use shared theme roles for changes that belong everywhere. Then review the whole journey: keyboard focus, long labels, narrow screens and a clear way to recover when something fails.
Keep a link to the source and note your intentional changes. Your next edit should begin with a clear decision, not another search.