Weave Code
Laraflash Laravel Package
devmarketer/laraflash
LaraFlash is a Laravel package for adding stylish flash notifications to your app. It offers a simple API for session-based messages, multiple notification types, custom styling, and Blade-ready output so you can display success, error, or info alerts with minimal setup.
A powerful and flexible flash notifications system. Improving over built-in Laravel Flash messaging functionality.
Frequently asked questions about Laraflash
- What is LaraFlash used for in Laravel?
- LaraFlash is a session-backed flash notification helper for Laravel. It lets controllers queue success, error, or info messages and render them in Blade views as Bootstrap-style alerts with a fluent API for title, type, and content. It is presentation convenience, not infrastructure, and has no database, queue, or external service dependency.
- How do I install devmarketer/laraflash?
- Install it with Composer using devmarketer/laraflash, then publish the package views or config if you need to customize the alert markup. On older Laravel versions you may need to register the service provider and LaraFlash facade manually, so check the package README for the exact namespace and alias. The integration is typically just controller calls plus one render directive in your layout.
- Does LaraFlash support Laravel 10 or Laravel 11?
- Not out of the box based on the package's current constraints. The codebase targets an older Laravel 5.x-era generation with legacy service provider and facade conventions and likely PHP 7.x constraints, so Laravel 10 or 11 on PHP 8.2+ may require a fork. You would need to widen composer.json constraints and re-verify provider registration, facade alias, and Blade syntax.
- How do I show LaraFlash messages in a Blade layout?
- Publish the package's Blade partial and include its render directive or include in your main layout where alerts should appear. The partial outputs Bootstrap-style alert markup, so place it inside your normal container or alert region. If you use Tailwind or a custom design system, expect to rewrite the partial to match your components.
- Can I customize LaraFlash notification types and alert styling?
- Yes, the fluent API supports chaining title, type, and content, and you can publish and edit the Blade partial to change markup and CSS classes. That makes it easy to map types like success, error, and info to your own alert styles. Because the bundled partial is Bootstrap-oriented, custom design systems usually require replacing it.
- Is LaraFlash safe to use with user-supplied notification text?
- Treat it carefully. The published partial is typically included with unescaped Blade output, so any notification content that interpolates user input is an XSS surface unless you escape at the call site or patch the partial. Developer-authored messages are lower risk, but confirm escaping before rollout if user data can reach a notification.
- Can LaraFlash stack multiple notifications in one request?
- Yes, stacking multiple notifications per request is one of its conveniences over a single session flash value. You can queue several messages with different types and render them together in the layout. The package stores this notification data in the session, so it follows the normal flash lifecycle.
- Does LaraFlash work with Livewire, Inertia, or API responses?
- LaraFlash is designed for classic server-rendered Blade pages using session flash data. It is not a good fit for API-first, SPA, or token-authenticated JSON consumers because the messages live in the session rather than in a response payload. For Livewire or Inertia, you would need a different delivery mechanism or a custom adapter.
- How is LaraFlash different from Laravel's built-in session flash?
- Laravel's session()->flash() gives you a single flashed value and leaves rendering and severity modelling to you. LaraFlash adds a fluent chainable API for title, type, and content, supports stacking multiple notifications, and ships a Blade render partial. Most of that overlap is easy to reproduce natively with a session flash, a Blade component, and a severity enum.
- Is LaraFlash maintained and suitable for production?
- It is a small, single-maintainer package with low commit velocity, limited stars, and no clear security policy or CI matrix, so treat it as a bus-factor-of-one dependency. Technical risk is mostly maintenance and compatibility rather than data integrity, since it has no persistence, migrations, queues, or network calls. For production, weigh a fork or a small in-house Blade alert component against the convenience it provides.
Weaver
How can I help you explore Laravel packages today?