Weave Code
Laravel Error Share Laravel Package
spatie/laravel-error-share
Share Laravel exceptions with a link so a colleague can inspect the full error details without screen sharing. Install as a dev dependency and a share button appears on every error page.
Share your Laravel errors to Flare
Frequently asked questions about Laravel Error Share
- How do I install spatie/laravel-error-share in Laravel?
- Run composer require spatie/laravel-error-share --dev in your Laravel project. The README describes no config file, manual service-provider registration, or migrations. After installation, trigger an exception and Ignition should show a share button.
- Which Laravel versions does spatie/laravel-error-share support?
- The technical assessment points to Laravel 10 through 13 on PHP 8.1+ as the plausible fit, assuming Ignition is present. However, the changelog is internally inconsistent: one entry claims Laravel 13 support while another references PHP 8.1 and Laravel 10/11. Verify compatibility with your lockfile and a test app instead of trusting the advertised matrix.
- Does spatie/laravel-error-share need a Flare account or API token?
- The README excerpt does not document whether the share endpoint requires a Flare account, API token, or anonymous posting. That gap matters because you need to know who controls the uploaded exception data. Confirm the endpoint behavior and vendor approval before rolling it out to a team.
- What data is uploaded when sharing a Laravel exception to Flare?
- An Ignition exception page can include stack traces with local file paths, environment values captured in exception context, request parameters, and sometimes literal credentials or tokens. Treat a share as third-party data egress and obtain security or data-governance sign-off before uploading real errors.
- Can spatie/laravel-error-share expose a share button in production?
- The package is designed as a dev dependency, so the standard mitigation is composer install --no-dev in production. If it ships anyway, a share route can appear on your production debug page and expose exception payloads for serious failures. Add an explicit deploy-pipeline check rather than relying on convention.
- Why is the share button missing from my Laravel Ignition error page?
- The package hooks into Laravel's Ignition error page when APP_DEBUG=true, so it will not add a button to Whoops or a custom error handler. If Ignition is active but the button is missing or the page itself breaks, check for a version incompatibility with your Laravel release. Pin an exact version and review the changelog for view-render fixes.
- How do I remove spatie/laravel-error-share from a Laravel app?
- Run composer remove spatie/laravel-error-share and commit the updated composer files. The README describes no migrations, config files, or manual service-provider steps to undo. Continue using composer install --no-dev in production so the package stays out of the production autoloader.
- Is spatie/laravel-error-share a replacement for Sentry or Bugsnag?
- It is not a general observability replacement; it adds a share link to Ignition error pages for local debugging. If your organization already standardizes on Sentry or Bugsnag, adding Flare sharing can create split-brain debugging and vendor overlap. Use it only if Flare is approved and the team values the quick link workflow.
- Is spatie/laravel-error-share maintained and safe to pin in a team project?
- The assessment notes a single-maintainer-org package with 43 stars and zero dependents, so there is no SLA. The changelog shows repeated fixes to the error-page view layer, including Laravel version and view-render breakages. Pin an exact version and verify the support matrix yourself rather than trusting the advertised matrix.
- How can I test spatie/laravel-error-share before using it with my team?
- Install it in a local or test Laravel app with Ignition enabled, trigger an exception, and confirm the share button appears and produces a usable link. Check what payload is sent and whether the endpoint requires Flare credentials before inviting teammates. Also verify that a production-style composer install --no-dev leaves no share route behind.
Weaver
How can I help you explore Laravel packages today?