https://github.com/wobsoriano/svelte-sonner/assets/13049130/4b9c250f-1431-4130-9c5b-5a4f8b0210c5

svelte-sonner

An opinionated toast component for Svelte. A port of Emil Kowalski's Sonner.

Quick start

Install it:

1npm i svelte-sonner
2# or
3yarn add svelte-sonner
4# or
5pnpm add svelte-sonner

Add <Toaster /> to your app, it will be the place where all your toasts will be rendered. After that, you can use toast() from anywhere in your app.

1<script>
2	import { Toaster, toast } from 'svelte-sonner';
3</script>
4
5<Toaster />
6<button onclick={() => toast('My first toast')}>Give me a toast</button>

Types

Default

Most basic toast. You can customize it (and any other type) by passing an options object as the second argument.

1toast('Event has been created');

With custom icon and description:

1import Icon from './Icon.svelte';
2
3toast('Event has been created', {
4	description: 'Monday, January 3rd at 6:00pm',
5	icon: Icon
6});

Success

Renders a checkmark icon in front of the message.

1toast.success('Event has been created');

Info

Renders a question mark icon in front of the message.

1toast.info('Event has new information');

Warning

Renders a warning icon in front of the message.

1toast.warning('Event has warning');

Error

Renders an error icon in front of the message.

1toast.error('Event has not been created');

Action

Renders a button.

1toast('Event has been created', {
2	action: {
3		label: 'Undo',
4		onClick: () => console.log('Undo')
5	}
6});

Promise

Starts in a loading state and will update automatically after the promise resolves or fails.

1toast.promise(() => new Promise((resolve) => setTimeout(resolve, 2000)), {
2	loading: 'Loading',
3	success: 'Success',
4	error: 'Error'
5});

You can pass a function to the success/error messages to incorporate the result/error of the promise.

1toast.promise(promise, {
2	loading: 'Loading...',
3	success: (data) => {
4		return `${data.name} has been added!`;
5	},
6	error: 'Error'
7});

Custom Component

You can pass a component as the first argument instead of a string to render custom component while maintaining default styling. You can use the headless version below for a custom, unstyled toast.

1toast(CustomComponent);

Updating a toast

You can update a toast by using the toast function and passing it the id of the toast you want to update, the rest stays the same.

1const toastId = toast('Sonner');
2
3toast.success('Toast has been updated', {
4	id: toastId
5});

Customization

Headless

You can use toast.custom to render an unstyled toast with custom component while maintaining the functionality.

1<script>
2	import { createEventDispatcher } from 'svelte';
3
4	const dispatch = createEventDispatcher();
5</script>
6
7<div>
8	This is a custom component <button onclick={() => dispatch('closeToast')}>close</button>
9</div>

1import HeadlessToast from './HeadlessToast.svelte';
2
3toast.custom(HeadlessToast);

Theme

You can change the theme using the theme prop. Default theme is light.

1<Toaster theme="dark" />

Position

You can change the position through the position prop on the <Toaster /> component. Default is bottom-right.

1<!-- Available positions -->
2<!-- top-left, top-center, top-right, bottom-left, bottom-center, bottom-right -->
3
4<Toaster position="top-center" />

Expanded

Toasts can also be expanded by default through the expand prop. You can also change the amount of visible toasts which is 3 by default.

1<Toaster expand visibleToasts={9} />

Styling

Styling can be done globally via toastOptions, this way every toast will have the same styling.

1<Toaster
2	toastOptions={{
3		style: 'background: red;',
4		class: 'my-toast',
5		descriptionClass: 'my-toast-description'
6	}}
7/>

You can also use the same props when calling toast to style a specific toast.

1toast('Event has been created', {
2	style: 'background: red;',
3	class: 'my-toast',
4	descriptionClass: 'my-toast-description'
5});

Tailwind CSS

The preferred way to style the toasts with tailwind is by using the unstyled prop. That will give you an unstyled toast which you can then style with tailwind.

1<Toaster
2	toastOptions={{
3		unstyled: true,
4		classes: {
5			toast: 'bg-blue-400',
6			title: 'text-red-400',
7			description: 'text-red-400',
8			actionButton: 'bg-zinc-400',
9			cancelButton: 'bg-orange-400',
10			closeButton: 'bg-lime-400'
11		}
12	}}
13/>

You can do the same when calling toast().

1toast('Hello World', {
2	unstyled: true,
3	classes: {
4		toast: 'bg-blue-400',
5		title: 'text-red-400 text-2xl',
6		description: 'text-red-400',
7		actionButton: 'bg-zinc-400',
8		cancelButton: 'bg-orange-400',
9		closeButton: 'bg-lime-400'
10	}
11});

Styling per toast type is also possible.

1<Toaster
2	toastOptions={{
3		unstyled: true,
4		classes: {
5			error: 'bg-red-400',
6			success: 'text-green-400',
7			warning: 'text-yellow-400',
8			info: 'bg-blue-400'
9		}
10	}}
11/>

Changing Icon

You can change the default icons using snippets:

1<Toaster>
2	{#snippet loadingIcon()}
3		<LoadingIcon />
4	{/snippet}
5	{#snippet successIcon()}
6		<SuccessIcon />
7	{/snippet}
8	{#snippet errorIcon()}
9		<ErrorIcon />
10	{/snippet}
11	{#snippet infoIcon()}
12		<InfoIcon />
13	{/snippet}
14	{#snippet warningIcon()}
15		<WarningIcon />
16	{/snippet}
17</Toaster>

Close button

Add a close button to all toasts that shows on hover by adding the closeButton prop.

1<Toaster closeButton />

Rich colors

You can make error and success state more colorful by adding the richColors prop.

1<Toaster richColors />

Custom offset

Offset from the edges of the screen.

1<Toaster offset="80px" />

Programmatically remove toast

To remove a toast programmatically use toast.dismiss(id). The toast() function returns the id of the toast.

1const toastId = toast('Event has been created');
2
3toast.dismiss(toastId);

You can also dismiss all toasts at once by calling toast.dismiss() without an id.

1toast.dismiss();

useSonner

You can use the useSonner hook to retrieve all visible toasts like below.

1const sonner = useSonner();
2
3$effect(() => console.log(sonner.toasts));

Duration

You can change the duration of each toast by using the duration property, or change the duration of all toasts like this:

1<Toaster duration={10000} />

1toast('Event has been created', {
2	duration: 10000
3});
4
5// Persisent toast
6toast('Event has been created', {
7	duration: Number.POSITIVE_INFINITY
8});

On Close Callback

You can pass onDismiss and onAutoClose callbacks. onDismiss gets fired when either the close button gets clicked or the toast is swiped. onAutoClose fires when the toast disappears automatically after it's timeout (duration prop).

1toast('Event has been created', {
2	onDismiss: (t) => console.log(`Toast with id ${t.id} has been dismissed`),
3	onAutoClose: (t) => console.log(`Toast with id ${t.id} has been closed automatically`)
4});

Keyboard focus

You can focus on the toast area by pressing ⌥/alt + T. You can override it by providing an array of event.code values for each key.

1<Toaster hotkey={['KeyC']} />

License

MIT