Weave Code
Laravel Ignition Laravel Package
spatie/laravel-ignition
Ignition is a beautiful, customizable error page for Laravel. Share errors via Flare, track production exceptions with notifications, and get helpful debugging tools. Supports Laravel 10+ on PHP 8.1+ (v2+).
A beautiful error page for Laravel applications.
Frequently asked questions about Laravel Ignition
- How do I install Ignition in a Laravel 10+ project?
- Run `composer require spatie/laravel-ignition` and execute `php artisan ignition:install`. This automatically registers the middleware in your `app/Http/Kernel.php` and publishes the config file. No further setup is needed for basic usage.
- Does Ignition work with Laravel 8 or 9?
- No, Ignition v2.x only supports Laravel 10+. For Laravel 8 or 9, use the legacy package `facade/ignition`. Check the [README](https://github.com/spatie/laravel-ignition) for version-specific instructions.
- Can I customize the error page design?
- Yes, Ignition allows full customization via Blade templates. Publish the views with `php artisan vendor:publish --tag=ignition-views`, then modify the files in `resources/views/vendor/ignition`. You can also override the default CSS.
- How do I integrate Ignition with Flare for error tracking?
- Add your Flare API key to `config/ignition.php` under `flare_api_key`. Enable error reporting in production by setting `report_errors` to `true`. This sends exceptions to Flare for tracking and notifications.
- Will Ignition slow down my production app?
- No, Ignition has minimal overhead in production. The error page only renders when exceptions occur, and Flare integration is optional. Disable Flare in production if not needed by setting `report_errors` to `false` in the config.
- Does Ignition support Livewire or Laravel Octane?
- Yes, Ignition is actively maintained for Livewire 3/4 and Laravel Octane. If you’re using older versions (e.g., Livewire 2), errors may not render correctly. Check the [documentation](https://flareapp.io/docs/ignition) for compatibility notes.
- How do I prevent sensitive data from leaking in error logs?
- Ignition automatically redacts sensitive headers (e.g., `Authorization`, `X-API-KEY`) in error pages. For additional safety, configure `ignition.php` to exclude sensitive context or use Laravel’s built-in exception handler to filter data before logging.
- Can I use Ignition in CI/CD pipelines?
- Yes, but disable it during tests to avoid clutter. Set the environment variable `IGNATION_ENABLED=false` in your CI config, or conditionally disable middleware in `app/Http/Kernel.php` using `app()->environment('ci')`.
- What alternatives exist for Laravel error pages?
- Alternatives include `laravel-debugbar` (for debugging tools), `whoops` (lightweight error pages), or `sentry-laravel` (for error tracking). Ignition stands out for its rich UI, Flare integration, and customization options tailored for Laravel.
- How do I extend Ignition with custom solutions (e.g., AI fixes)?
- Use the `SolutionProvider` interface to add custom solutions. Register your provider in `config/ignition.php` under `solutions`. This allows you to inject team-specific tools, like AI-driven fixes or internal dashboards, into the error page.
Weaver
How can I help you explore Laravel packages today?