Weave Code
Laravel Error Share Laravel Package
spatie/laravel-error-share
Adds a “Share” button to Laravel exception pages so you can generate a link and let teammates view the full error details without screen sharing. Install as a dev dependency and share local exceptions instantly.
Share your Laravel errors
Frequently asked questions about Laravel Error Share
- How do I install spatie/laravel-error-share for Laravel 13?
- Run `composer require spatie/laravel-error-share --dev` in your project. The package is officially supported for Laravel 13 and hooks into the default exception handler without extra configuration. Ensure you also have `spatie/laravel-flare` installed for full functionality.
- Will this work with Laravel 11?
- The package is unofficially compatible with Laravel 11, but it’s actively maintained for Laravel 12/13. Test thoroughly in your environment, as some edge cases (like view compilation) may require adjustments. Check the [GitHub issues](https://github.com/spatie/laravel-error-share/issues) for Laravel 11-specific fixes.
- Do I need to configure anything after installation?
- No configuration is required for basic usage. The package automatically adds a ‘Share’ button to Laravel’s default error pages. If you need customization (e.g., modifying the Blade view), publish the assets with `php artisan vendor:publish --tag=error-share-views` and edit `resources/views/vendor/error-share.blade.php`.
- Can I use this in production?
- This package is designed as a **development-only** tool (installed via `--dev`). It won’t appear in production builds. For production debugging, consider using Flare’s remote monitoring or other error-tracking services like Sentry or Bugsnag, which are built for live environments.
- How does the ‘Share’ button generate a link?
- When clicked, the button creates a unique, time-limited URL that redirects to your Flare dashboard, pre-filtered to show the exact exception. The link includes all relevant context (request data, stack traces, etc.) captured by Flare’s PHP extension. No sensitive data is exposed unless explicitly configured in Flare.
- What happens if Flare isn’t installed?
- The package **requires** `spatie/laravel-flare` to function. Without it, the ‘Share’ button will appear but won’t generate usable links. Install Flare first with `composer require spatie/laravel-flare --dev`, configure it in `.env` (e.g., `FLARE_ID=your_id`), and ensure the PHP extension is enabled.
- Can I customize the share button or error details?
- Yes. Publish the default view with `php artisan vendor:publish --tag=error-share-views` to override `resources/views/vendor/error-share.blade.php`. You can modify the button’s appearance, add metadata (e.g., user IDs), or extend the shared context by hooking into Flare’s `flare:error` event in your `EventServiceProvider`.
- Will this slow down my application?
- No. The package only activates during exception rendering and adds negligible overhead. It doesn’t run on every request or query. Performance impact is limited to the time taken to generate the share link (milliseconds), which only occurs when an error is thrown.
- How do I test if error sharing works locally?
- Trigger a test error in a route (e.g., `abort(500)`), then click the ‘Share’ button. Verify the link opens in your browser and shows the error in Flare’s dashboard. Check Flare’s logs or the network tab to confirm the error was captured. For automated testing, use Laravel’s `expectException()` in PHPUnit.
- Are there alternatives to this package?
- For Laravel, alternatives include **Laravel Debugbar** (for local inspection) or **Sentry/Laravel Error Pages** (for production tracking). Unlike this package, those tools don’t focus on *sharing* errors via a direct link but offer broader debugging features. If you need a lightweight, Flare-specific solution, this remains the most integrated option.
Weaver
How can I help you explore Laravel packages today?