Weave Code
Laravel Ignition Laravel Package
spatie/laravel-ignition
Ignition is a beautiful, customizable error page for Laravel apps. It can also share errors publicly on Flare and, with a valid API key, track production errors and notify you when they occur.
Ignition is a beautiful, customizable error page for Laravel applications. It transforms exceptions into a clean, readable interface that helps you debug faster, and it can publish errors directly to Flare for tracking and notifications.
- Gorgeous, interactive error screens with stack traces
- One-click error sharing via Flare
- Production error tracking and alerts with a Flare API key
- Customizable rendering for your app's needs
- Supports Laravel 10+ on PHP 8.1 or higher
Frequently asked questions about Laravel Ignition
- How do I install spatie/laravel-ignition in a Laravel application?
- In most Laravel 10+ projects it is already there: the laravel/laravel skeleton and the framework's dev requirements pull it in transitively, so many teams never install it deliberately. If you do need it explicitly, run composer require --dev spatie/laravel-ignition. Package auto-discovery wires up the exception renderer, so the improved error page works immediately with no further configuration.
- Which Laravel and PHP versions does spatie/laravel-ignition support?
- The 2.x line requires Laravel 10+ and PHP 8.1 or higher, and recent releases test against PHP 8.5, Symfony 8 and Laravel 13. Support windows move inside the major: v2.10.0 dropped Laravel 10 and Livewire 2, v2.11.0 added Laravel 13, and v2.12.0 moved to spatie/ignition ^1.16. Teams on Laravel 8 or 9 should stay on 1.x, and Laravel 5 to 7 use the older facade/ignition package.
- Should spatie/laravel-ignition be installed in production?
- No. It is a require-dev dependency whose value is local and staging diagnostics, so production builds should use composer install --no-dev and assert that APP_DEBUG is false. Make that an automated CI check rather than a convention someone remembers. The package itself adds nothing your end users see.
- Is it dangerous to run Ignition with APP_DEBUG=true?
- Yes, and this is the single critical failure mode for the package. Ignition renders environment variables, request payloads, session state and query bindings, so any path where APP_DEBUG=true reaches a live environment turns the error page into an exfiltration vector. It is a deployment-hygiene control rather than a package defect, but it is the risk your team must explicitly own.
- Does Ignition send my error data to Flare or OpenAI?
- Only if you opt in. Adding a Flare API key enables production error tracking and notifications through Spatie's infrastructure, and the AI solutions feature sends exception context to OpenAI when open_ai_key is configured. Both need explicit approval under any data-handling or source-code policy. With no keys configured, error rendering stays inside your own environment.
- How do I publish and customize the ignition.php config file?
- Configuration is opt-in: publish the package config with php artisan vendor:publish to create config/ignition.php, then adjust only the options you actually need. Most teams never publish it because the defaults are fine for local development. If you do publish it, review the file like any other code change, especially any setting that enables external reporting.
- Can Ignition run alongside Sentry, Bugsnag, Telescope and Horizon?
- Usually yes, but ordering matters and should be smoke-tested rather than assumed. Ignition hooks Laravel's exception handler, so its interaction with other reporters depends on how each one is registered. After any change to your observability stack, confirm in staging that errors are still captured by everything you rely on.
- How do I get clickable stack trace editor links working with Docker or Laravel Sail?
- Ignition turns stack frames into editor links, but it needs to know how paths inside your container map to paths on your host machine. With Sail or Docker you configure those path mappings in config/ignition.php so remote paths resolve correctly. Whether you standardize that config for the whole team or leave it per developer is a governance choice, not a technical limit.
- Is spatie/laravel-ignition actively maintained, and does it drop Laravel versions within a major?
- Yes, it is well maintained and releases track new Laravel and Symfony versions quickly. The caveat is that support windows shift inside a major, with minor releases dropping Laravel 10 and Livewire 2 support, so read the changelog instead of trusting a loose version constraint. Security fixes also arrive regularly, including patches in v2.12.0 and v1.7.1 for view data leaking into laravel.log.
- What are the alternatives to spatie/laravel-ignition?
- The closest alternatives are Laravel's built-in error page and, on older versions, Whoops. Sentry, Bugsnag and Telescope solve production observability rather than local debugging, so most teams keep Ignition for development and pair it with a separate production tracker. Because it ships with the Laravel skeleton, opting out usually means deliberately replacing the default renderer.
Weaver
How can I help you explore Laravel packages today?