Filament has a few requirements to run:

  • PHP 8.0+
  • Laravel v8.0+
  • Livewire v2.0+

Notifications come pre-installed inside the admin panel 2.x, but you must still follow the installation instructions below if you're using it in the rest of your app.

First, require the notifications package using Composer:

composer require filament/notifications:"^2.0"

New Laravel projects

To get started with notifications quickly, you can set up Livewire, Alpine.js and Tailwind CSS with these commands:

php artisan notifications:install
npm install
npm run dev

These commands will ruthlessly overwrite existing files in your application, hence why we only recommend using this method for new projects.

You're now ready to start sending notifications!

Filament Notifications

Existing Laravel projects

The package uses the following dependencies:

You may install these through NPM:

npm install alpinejs @awcodes/alpine-floating-ui postcss tailwindcss --save-dev

Configuring Tailwind CSS

To finish installing Tailwind, you must create a new tailwind.config.js file in the root of your project. The easiest way to do this is by running npx tailwindcss init.

In tailwind.config.js, add custom colors used by notifications:

import colors from 'tailwindcss/colors'
export default {
content: [
theme: {
extend: {
colors: {
danger: colors.rose,
warning: colors.yellow,

Of course, you may specify your own custom primary, success, warning and danger colors, which will be used instead.

Bundling assets

New Laravel projects use Vite for bundling assets by default. However, your project may still use Laravel Mix. Read the steps below for the bundler used in your project.


If you're using Vite, you should manually install Autoprefixer through NPM:

npm install autoprefixer --save-dev

Create a postcss.config.js file in the root of your project, and register Tailwind CSS and Autoprefixer as plugins:

export default {
plugins: {
tailwindcss: {},
autoprefixer: {},

You may also want to update your vite.config.js file to refresh the page after Livewire components have been updated:

import { defineConfig } from 'vite';
import laravel, { refreshPaths } from 'laravel-vite-plugin';
export default defineConfig({
plugins: [
input: [
refresh: [

Laravel Mix

In your webpack.mix.js file, register Tailwind CSS as a PostCSS plugin:

const mix = require('laravel-mix')
mix.js('resources/js/app.js', 'public/js')
.postCss('resources/css/app.css', 'public/css', [

Configuring styles

In /resources/css/app.css, import Tailwind CSS:

@tailwind base;
@tailwind components;
@tailwind utilities;

Configuring scripts

In /resources/js/app.js, import Alpine.js, Alpine Floating UI and the filament/notifications plugin, and register them:

import Alpine from 'alpinejs'
import AlpineFloatingUI from '@awcodes/alpine-floating-ui'
import NotificationsAlpinePlugin from '../../vendor/filament/notifications/dist/module.esm'
window.Alpine = Alpine

Compiling assets

Compile your new CSS and JS assets using npm run dev.

Configuring layout

Finally, create a new resources/views/layouts/app.blade.php layout file for Livewire components:

<!DOCTYPE html>
<html lang="{{ str_replace('_', '-', app()->getLocale()) }}">
<meta charset="utf-8">
<meta name="application-name" content="{{ config('') }}">
<meta name="csrf-token" content="{{ csrf_token() }}">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>{{ config('') }}</title>
<style>[x-cloak] { display: none !important; }</style>
@vite(['resources/css/app.css', 'resources/js/app.js'])
<body class="antialiased">
{{ $slot }}

You're now ready to start sending notifications!

Publishing configuration

If you wish, you may publish the configuration of the package using:

php artisan vendor:publish --tag=notifications-config


To upgrade the package to the latest version, you must run:

composer update
php artisan filament:upgrade

We recommend adding the filament:upgrade command to your composer.json's post-update-cmd to run it automatically:

"post-update-cmd": [
// ...
"@php artisan filament:upgrade"
Edit on GitHub

Still need help? Join our Discord community or open a GitHub discussion