- Is speerit/airbrake-bundle compatible with Laravel?
- No, it is a Symfony2 bundle, not a Laravel package. It relies on Symfony's bundle and dependency injection system, so Laravel's service container and package discovery will not wire it automatically. You would need a custom adapter or use the underlying Airbrake client directly.
- How do I install speerit/airbrake-bundle in a Laravel application?
- You cannot install it as a native Laravel package. Composer require may work, but it will not integrate with Laravel's exception handler. You would need to manually register Symfony services or build an adapter, which adds little value over a maintained Laravel error-reporting package.
- Does speerit/airbrake-bundle support Laravel 10 or 11?
- No, the package targets Symfony2, which is end-of-life. It has no Laravel service provider, facade, or auto-discovery. Its dependencies are pinned to legacy versions like phpbrake 0.5, so it will likely conflict with modern Laravel and Symfony components.
- Can I use speerit/airbrake-bundle with Laravel's exception handler?
- Not directly. Laravel's App\Exceptions\Handler expects a Laravel-native reporter. You could wrap the bundle's services in a custom adapter and call it from the handler, but that is fragile. A maintained Laravel package or a thin wrapper around the official Airbrake PHP SDK is safer.
- What are the alternatives to speerit/airbrake-bundle for Laravel?
- For Laravel, consider maintained error-tracking packages like Sentry, Bugsnag, Rollbar, or Flare, or a Laravel-specific Airbrake integration if available. You can also use the official Airbrake PHP SDK directly via a small service provider and queued job.
- Is speerit/airbrake-bundle maintained and safe for production?
- It is effectively unmaintained: only 1 star, 0 dependents, and the latest release 2.2.0 is just a phpbrake 0.5 dependency bump. Symfony2 is end-of-life, so security patches and PHP compatibility fixes are missing. Avoid new adoption in production; if inherited, isolate and replace it.
- What changed in speerit/airbrake-bundle 2.2.0?
- Version 2.2.0 only bumps the transitive phpbrake dependency to 0.5. It does not add Laravel support, a service provider, or modern SDK features. Treat it as a maintenance bump, not a signal to invest in the bundle.
- How do I configure Airbrake credentials with speerit/airbrake-bundle?
- In Symfony2, you configure project ID, API key, and environment via the bundle's config. In Laravel, there is no native config; you would need to pass credentials to the underlying client manually. Ensure you use Airbrake API v3 credentials and scrub secrets before reporting.
- Does speerit/airbrake-bundle support asynchronous error reporting or PII scrubbing?
- No, the bundle and phpbrake 0.5 lack modern features like async delivery, breadcrumbs, sampling, and privacy controls. If you need async reporting in Laravel, implement a queued job around a maintained notifier and add your own scrubbing logic.
- How should I migrate from speerit/airbrake-bundle to a Laravel-native solution?
- First confirm if Airbrake is mandatory; if not,switch to Sentry, Bugsnag, or Flare. If yes, isolate error reporting behind an ErrorReporter interface, implement it with the official Airbrake PHP SDK or a maintained package, hook it into App\Exceptions\Handler, and queue reports. Then remove the legacy bundle and test for double-reporting.