mckenziearts/laravel-notify
Composer 安装命令:
composer require mckenziearts/laravel-notify
包简介
Flexible flash notifications for Laravel
README 文档
README
Introduction
Laravel Notify is a lightweight Laravel package for displaying backend-driven notifications in your application.
Installation
You can install the package using composer
composer require mckenziearts/laravel-notify
You can publish the configuration file and assets by running:
php artisan vendor:publish --tag=notify-assets php artisan vendor:publish --tag=notify-config
Option 1: With Tailwind CSS & Alpinejs
If your project already uses Tailwind CSS 4.x, follow these steps to integrate Laravel Notify directly into your build process.
Step 1: Configure Tailwind to scan package files
In your resources/css/app.css, add the package's Blade files to Tailwind's content sources using the @source directive:
@import "tailwindcss"; @source "../../vendor/mckenziearts/laravel-notify/resources/views/**/*.blade.php";
Step 2: Import the JavaScript
In your resources/js/app.js, import Alpine.js if you haven't already:
import Alpine from 'alpinejs' window.Alpine = Alpine Alpine.start()
Step 3: Add the notification component to your layout
In your main Blade layout file (e.g., resources/views/layouts/app.blade.php):
<!-- Add notification component before closing body tag --> <x-notify::notify />
Step 4: Build your assets
npm run build
# or for development
npm run dev
✅ Done! Tailwind will automatically generate CSS for all the notification styles used in the package.
Option 2: Without Tailwind CSS
If you don't use Tailwind CSS in your project, you can use the pre-compiled CSS and JavaScript files.
Add directives to your layout
<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Laravel Notify</title> <!-- Add Laravel Notify CSS --> @notifyCss </head> <body> <!-- Add notification component --> <x-notify::notify /> <!-- Add Laravel Notify JavaScript --> @notifyJs </body> </html>
✅ Done! The pre-compiled assets will be loaded from your public/vendor/mckenziearts/laravel-notify/dist/ directory.
Usage
Within your controllers, before you perform a redirect call the notify method with a title.
public function store() { notify() ->success() ->title('⚡️ Laravel Notify is awesome!') ->send(); return back(); }
Type of notifications
Laravel Notify actually display 5 types of notifications
toastnotification, (The default notification for Laravel Notify)
notify() ->success() ->title('Welcome to Laravel Notify ⚡️') ->send();
connectifynotification, example of basic usage
notify() ->model(NotificationModel::Connect) ->success() ->title('Connection Found') ->message('Success Message Here') ->send();
drakify(😎) notification, displays an alert only
// For success alert notify() ->model(NotificationModel::Drake) ->success() ->send(); // or notify() ->model(NotificationModel::Drake) ->error() ->send(); // for error alert
smileynotification, displays a simple custom toast notification using the smiley (😊) emoticon
notify() ->model(NotificationModel::Smiley) ->success() ->title('You are successfully reconnected') ->send();
emotifynotification, displays a simple custom toast notification using a vector emoticon
notify() ->model(NotificationModel::Emotify) ->success() ->title('You are awesome, your data was successfully created') ->send();
Setting a duration
By default, notifications are shown for 5 seconds before they're automatically closed. You may customize this using the duration() method:
notify() ->success() ->title('Saved successfully') ->duration(3000) // 3 seconds ->send();
If you'd like to make a notification stay open until the user manually closes it, you can set a very long duration:
notify() ->warning() ->title('Important notice') ->duration(999999) // ~16 minutes ->send();
You can also configure a default duration for all notifications in the config/notify.php file:
'timeout' => env('NOTIFY_TIMEOUT', 5000),
Adding Actions to Notifications
You can add interactive actions to your notifications, allowing users to perform tasks directly from the notification. Actions support both navigation (redirecting to a URL) and execution (calling a controller action).
Note: Actions are supported only for the following notification models: Toast, Connect, Smiley, and Emotify. The Drake model does not support actions.
Basic Usage
use Mckenziearts\Notify\Action\NotifyAction; notify() ->success() ->title('User deleted successfully') ->actions([ NotifyAction::make() ->label('Undo') ->action(route('users.restore', $user->id)), NotifyAction::make() ->label('View All') ->url(route('users.index')), ]) ->send();
URL Actions (Navigation)
Use the url() method to redirect users to another page. This creates a simple link (GET request):
NotifyAction::make() ->label('View details') ->url(route('users.show', $user->id));
You can open URLs in a new tab using the openUrlInNewTab() method:
NotifyAction::make() ->label('Read documentation') ->url('https://laravel.com/docs') ->openUrlInNewTab();
Action Actions (Execution)
Use the action() method to execute a controller action. This sends an HTTP request (POST by default) to your controller:
NotifyAction::make() ->label('Restore') ->action(route('users.restore', $user->id));
You can specify the HTTP method using the method() method:
// DELETE request NotifyAction::make() ->label('Delete permanently') ->action(route('users.force-delete', $user->id)) ->method('DELETE'); // PUT request NotifyAction::make() ->label('Update status') ->action(route('users.activate', $user->id)) ->method('PUT');
If you don't specify a method, it defaults to POST.
Complete Example
public function destroy(User $user) { $user->delete(); notify() ->success() ->title('User deleted') ->message('The user has been moved to trash') ->actions([ NotifyAction::make() ->label('Undo') ->action(route('users.restore', $user->id)) ->method('POST'), NotifyAction::make() ->label('View Trash') ->url(route('users.trash')) ->openUrlInNewTab(), ]) ->send(); return redirect()->route('users.index'); }
Custom Styling
You can customize the appearance of action buttons using the classes() method:
NotifyAction::make() ->label('Delete') ->action(route('users.delete', $user->id)) ->method('DELETE') ->classes('text-red-600 hover:text-red-500 font-bold');
Important Notes
- Mutual Exclusivity: You cannot use both
action()andurl()on the same action. Choose one or the other. - Method Restriction: The
method()function can only be used withaction(). Using it withurl()will throw an exception. - New Tab Restriction: The
openUrlInNewTab()function can only be used withurl(). Using it withaction()will throw an exception. - Auto-close: When an action is executed successfully, the notification automatically closes.
- CSRF Protection: Action requests automatically include CSRF tokens and proper headers.
- Supported Models: Actions work with
Toast,Connect,Smiley, andEmotifynotification models only.
Preset Notifications
If you have a specific notification that is used across multiple different places in your system, you can define it as a preset notification in your config file. This makes it easier to maintain commonly used notifications in one place. Read how to define preset messages in the Config section below.
As an example, to use a preset notification you have defined called 'common-notification', use the following:
notify()->preset('common-notification')->send();
You can override any of the values that are set in the config if you need to. For example, this could be useful if you have a common notification across, but you want to change the icon in one particular place that it's used without having to manually write out a new notification.
To do this, simply pass in an array that has the key of the attribute that you want to override and the value you want to override it with.
As an example, we could override the 'title' of our 'common-notification' by using the following:
notify()->preset('common-notification', ['title' => 'This is the overridden title'])->send();
Config
Config file are located at config/notify.php after publishing NotifyServiceProvider.
You can define preset notifications in the config file using the following structure:
use Mckenziearts\Notify\Enums\NotificationType; use Mckenziearts\Notify\Enums\NotificationModel; 'preset-messages' => [ 'user-updated' => [ 'type' => NotificationType::Success, 'model' => NotificationModel::Toast, 'title' => 'User Updated', 'message' => 'The user has been updated successfully.', ], 'user-deleted' => [ 'type' => NotificationType::Success, 'model' => NotificationModel::Toast, 'title' => 'User Deleted', 'message' => 'The user has been deleted successfully.', ], ],
The example above shows the config for two preset notifications: 'user-updated' and 'user-deleted'.
Credits
mckenziearts/laravel-notify 适用场景与选型建议
mckenziearts/laravel-notify 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 1.1M 次下载、GitHub Stars 达 1.73k, 最近一次更新时间为 2019 年 11 月 05 日, 在 PHP 生态内属于活跃度较高的组件。
它主要适用于以下技术方向: 「notification」 「laravel」 「laravel-notify」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。
我们在过去多个企业项目中使用过 mckenziearts/laravel-notify 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 mckenziearts/laravel-notify 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
与 mckenziearts/laravel-notify 相关的其它包
同方向 / 同关键字的高下载量 PHP Composer 包推荐,方便对比选型:
This package makes it easy to send notifications via AfricasTalking with Laravel
Apple Push Notification & Feedback Provider
Throttle notifications on a per-channel basis
Flexible flash notifications for Laravel
Extensible library for building notifications and sending them via different delivery channels.
Simple javascript toast notifications
统计信息
- 总下载量: 1.1M
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 1738
- 点击次数: 25
- 依赖项目数: 5
- 推荐数: 0
其他信息
- 授权协议: MIT
- 更新时间: 2019-11-05
