Toast
A toast component with native features
Toast
Use to show feedback to user interactions
Features
Automatically closes
Pause closing on hover, focus, window blur and mobile touch
Supports closing via swipe gesture
Easily animatable with Tamagui's animation drivers
Native toasts included for Android, iOS and web (notification API)
Usage
Imperative API
This API offers a nice imperative interface, support for native toasts with a lot of control.
Installation
For native support on mobile, run yarn add burnt to add burnt, then rebuild your React Native app. React Native requires sub-dependencies with native dependencies always be hoisted to your apps package.json and Toast relies on the amazing Burnt library by Fernando Rojo to provide its native functionality.
Note: Burnt will not work with Expo Go.
Usage
To display the toast natively, you should either pass an array of native platforms (native: ["ios", "web"]), a single platform or true for all platforms.
import { Button } from 'tamagui' // or '@tamagui/button'import { Toast, ToastImperativeProvider, ToastProvider, useToast } from 'tamagui' // or '@tamagui/toast'const options = { native: 'mobile' }export default () => (<ToastProvider><ToastImperativeProvider options={options}><CurrentToast /><MyPage /></ToastImperativeProvider><ToastViewport /></ToastProvider>)const CurrentToast = () => {const { currentToast } = useToast()// only show the component if it's present and not handled by native toastif (!currentToast || currentToast.isHandledNatively) return nullreturn (<Toast key={currentToast.id}><Toast.Title>{currentToast.title}</Toast.Title><Toast.Description>{currentToast.message}</Toast.Description></Toast>)}const MyPage = () => {const { show } = useToast()return (<Button onPress={() => show('Done!', { message: 'Form submitted successfully.' })}>Show Toast</Button>)}
Barebone API
This API does not support native toasts. For native toasts, use the Imperative API.
Single Toast
export default () => {const [open, setOpen] = React.useState(false)const timerRef = React.useRef(0)React.useEffect(() => {return () => clearTimeout(timerRef.current)}, [])return (<YStack ai="center"><Button onPress={() => { setOpen(false) window.clearTimeout(timerRef.current) timerRef.current = window.setTimeout(() => { setOpen(true) }, 150) }} >Single Toast</Button><Toast onOpenChange={setOpen} open={open} animation="100ms" enterStyle={{ x: -20, opacity: 0 }} exitStyle={{ x: -20, opacity: 0 }} opacity={1} x={0} ><Toast.Title>Subscribed!</Toast.Title><Toast.Description>We'll be in touch.</Toast.Description></Toast></YStack>)}
Multiple Toast
To use multiple toasts, you should pass multipleToasts to your ToastViewport.
Otherwise there’ll be issues when swipe-dismissing or animating toasts.
export default () => {const [savedCount, setSavedCount] = React.useState(0)return (<YStack ai="center"><Button onPress={() => { setSavedCount((old) => old + 1) }} >Show toast</Button>{[...Array(savedCount)].map((_, index) => (<Toast key={index} animation="100ms" enterStyle={{ x: -20, opacity: 0 }} exitStyle={{ x: -20, opacity: 0 }} opacity={1} x={0} ><Toast.Title>Subscribed!</Toast.Title><Toast.Description>We'll be in touch.</Toast.Description></Toast>))}</YStack>)}
API
ToastProvider
Your toasts should be wrapped within a ToastProvider. This is usually done at the root of your application.
Props
label
string
Default:
NotificationAn author-localized label for each toast. Used to help screen reader users associate the interruption with a toast.
duration
number
Default:
5000Time in milliseconds that each toast should remain visible for. This could be overwritten at the toast level as well.
swipeDirection
SwipeDirection
Default:
rightDirection of pointer swipe that should close the toast.
swipeThreshold
number
Default:
50Distance in pixels that the swipe must pass before a close is triggered.
id
string
Default:
A unique generated IDToastViewport
The portal for toasts to be directed to. Should be inside ToastProvider. Beyond Stack Props, adds:
Props
hotkey
string[]
Default:
['F8']The keys to use as the keyboard shortcut that will move focus to the toast viewport.
label
string
Default:
Notifications ({hotkey})An author-localized label for the toast viewport to provide context for screen reader users when navigating page landmarks. The available `{hotkey}` placeholder will be replaced for you.
name
string
Used to reference the viewport if you want to have multiple viewports in the same provider.
multipleToasts
boolean
Pass this when you want to have multiple/duplicated toasts.
Toast
Contains the Title, Description, Action and Close component. Should be inside ToastProvider. Extends Stack and adds:
Props
forceMount
boolean
Used to force mounting when more control is needed. Useful when controlling animation with React animation libraries.
type
'foreground' | 'background'
Control the sensitivity of the toast for accessibility purposes. For toasts that are the result of a user action, choose foreground. Toasts generated from background tasks should use background.
duration
number
Time in milliseconds that toast should remain visible for. Overrides value given to `ToastProvider`.
defaultOpen
boolean
The open state of the dialog when it is initially rendered. Use when you do not need to control its open state.
open
boolean
The controlled open state of the dialog. Must be used in conjunction with `onOpenChange`.
onOpenChange
(open: boolean): void
Event handler called when the open state of the dialog changes.
onEscapeKeyDown
(): DismissableProps['onEscapeKeyDown']
Event handler called when the escape key is down. It can be prevented by calling `event.preventDefault`.
onPause
(): void
Event handler called when the dismiss timer is paused. On web, this occurs when the pointer is moved over the viewport, the viewport is focused or when the window is blurred. On mobile, this occurs when the toast is touched.
onResume
(): void
Event handler called when the dismiss timer is resumed. On web, this occurs when the pointer is moved away from the viewport, the viewport is blurred or when the window is focused. On mobile, this occurs when the toast is released.
onSwipeStart
(event: SwipeEvent): void
Event handler called when starting a swipe interaction. It can be prevented by calling `event.preventDefault`.
onSwipeMove
(event: SwipeEvent): void
Event handler called during a swipe interaction. It can be prevented by calling `event.preventDefault`.
onSwipeCancel
(event: SwipeEvent): void
Event handler called at the cancellation of a swipe interaction. It can be prevented by calling `event.preventDefault`.
onSwipeEnd
(event: SwipeEvent): void
Event handler called at the end of a swipe interaction. It can be prevented by calling `event.preventDefault`.
viewportName
string
Default:
defaultThe viewport's name to send the toast to. Used when using multiple viewports and want to forward toasts to different ones.
Toast.Title
Should be inside Toast. Extends SizableText.
Toast.Description
Should be inside Toast. Extends SizableText.
Toast.Close
Should be inside Toast. Extends Stack. You can pass asChild to this component and use a custom <Button> inside.
Toast.Action
Should be inside Toast. Extends Stack. You can pass asChild to this component and use a custom <Button> inside.
ToastImperativeProvider
Wrap components within this provider to use useToast() inside them.
Props
options
ToastImperativeOptions
Used to provide defaults to imperative API. Options can be overwritten when calling `show()`.
useToast
Used when using the imperative API.
Returns
currentToast
ToastData | null
The information about the current toast to show such as title, message, duration, etc.
show
(title: string, showOptions?: ShowToastOptions): void
Call it to show a new toast. If you're using native toasts, you can pass native options using `burntOptions` or `notificationOptions` depending on the native platform (mobile/web).
hide
(): void
Call it to hide the currently displayed toast.
FAQ
How to change the placement of toasts?
Native toasts
- iOS (burnt): Supports top or bottom placements. Adjustable by passing
fromtoburntOptions:
<ToastImperativeProvider options={{ burntOptions: { from: 'bottom' } }}>
- Android (burnt): Not supported.
- Web (Notification API): Not supported.
Non-native toasts
You should change the positioning of your <ToastViewport>. For instance, if you want them to appear from top right:
<ToastViewport flexDirection="column-reverse" top={0} right={0} />
Or for bottom center:
<ToastViewport flexDirection="column" bottom={0} left={0} right={0} />
When using multiple toasts, you can change the order of toasts by setting
flexDirection to column or column-reverse. Or even have them stack horizontally
using row or row-reverse.
How to show non-native toasts within safe area on mobile?
Install react-native-safe-area-context if you haven’t, wrap your app inside <SafeAreaProvider>, and use the safe area insets to position the viewport inside the safe area.
import { useSafeAreaInsets } from 'react-native-safe-area-context'const SafeToastViewport = () => {const { left, top, right } = useSafeAreaInsets()return (<ToastViewport flexDirection="column-reverse" top={top} left={left} right={right} />)}
Can I have multiple viewports?
Yes, but you will have to name them and then reference the viewport name on the <Toast> component. for instance:
const App = () => {return (<ToastProvider><ToastViewport /> // name will be "default"<ToastViewport name="viewport-custom" /></ToastProvider>)}const MyComponent = () => {return <Toast> // goes to default viewport // ...</Toast>}const MyComponent2 = () => {return <Toast viewportName="viewport-custom">// ...</Toast>}