Getting Started

Install the package with composer require yoeunes/toastr.
Publish assets using php artisan flasher:install. This installs the necessary JavaScript/CSS (via PHPFlasher’s flasher-toastr-laravel integration) into your public/ directory.
Start using it in controllers: call toastr()->success('...'), error(), warning(), or info() before a redirect or response.
Ensure your main layout (e.g., resources/views/layouts/app.blade.php) includes {{ flasher()->render() }} after </html> or before closing </body> — this renders the toasts and scripts.

Implementation Patterns

Controller-Level Notifications: Use toastr() (or flash()->toastr(), both work) right before redirects. Ideal for CRUD operations: success after create/update, errors on failure.
Bulk Notifications: Chain multiple calls (e.g., toastr()->success('Saved')->warning('Retry count reset')), though avoid overuse per request.
Custom Config via Flasher: Use flasher()->addOptions(['positionClass' => 'toast-bottom-right']) or config via config/flasher.php (published during flasher:install). The config mirrors PHPFlasher options, including global settings like timeout, closeButton, progressBar.
Async Support: Works seamlessly with Laravel’s Livewire (call toastr() in event methods) and Filament actions/resources out of the box.
Testing Helpers: In tests, use flasher()->getMessages() to assert toast presence/absence after a request.

Positioning Quirk: Default positionClass is 'toast-top-right'. Change globally in config/flasher.php or use toastr()->position('toast-bottom-left') per-message.
Blade Rendering Order: If {{ flasher()->render() }} is placed before </html>, JS/CSS may load after the DOM, causing timing issues. Move it inside <body>, just before </body>, for reliable toast display.
Version 3 Depends on PHPFlasher: You no longer install toastr.js manually — it’s bundled automatically. Avoid mixing with direct toastr CDN scripts to prevent conflicts.
Debugging Missing Toasts:
- Confirm flasher.js and flasher.css are served (check DevTools Network tab after redirect).
- Ensure toastr JavaScript is loaded (global toastr object should exist in console).
- Check session('flash_messages') isn’t cleared too early (e.g., by middleware redirects before response).
Extending Functionality: Override PHPFlasher services via Laravel’s service provider bindings, or use flasher()->template('my-template') for custom toast markup (if needed via PHPFlasher extension).