Weave Code
Bugsnag Bundle Laravel Package
simpleweb/bugsnag-bundle
Symfony bundle that integrates Bugsnag error monitoring into your application, helping capture exceptions and report them with context so you can track and debug production issues more effectively.
An integration bundle for the bugsnag-php module into the Symfony2 framework.
Frequently asked questions about Bugsnag Bundle
- Does simpleweb/bugsnag-bundle work with Laravel?
- No. It is a Symfony2 bundle that registers the Bugsnag PHP notifier through Symfony's dependency injection container and kernel exception listener. It ships no Laravel service provider, facade, publishable config, or package auto-discovery manifest, so Composer will install it but Laravel will never boot it. For a Laravel application the correct choice is bugsnag/bugsnag-laravel.
- What is the Laravel alternative to simpleweb/bugsnag-bundle?
- Use the first-party bugsnag/bugsnag-laravel package. It is auto-discovered, exposes config/bugsnag.php for publishing, and hooks into App\Exceptions\Handler::report() so exceptions are reported without custom glue code. Migrating to it is cheaper than hand-wiring this Symfony bundle into Laravel.
- How do I install and register simpleweb/bugsnag-bundle in a Symfony application?
- Require it with Composer and enable the bundle in your kernel or bundles.php file, then supply your Bugsnag API key through bundle configuration. The bundle wires the notifier into the service container and attaches a kernel exception listener so uncaught exceptions are reported automatically. It is only viable inside a legacy Symfony 2.3 to 2.8 style application whose Composer constraints still resolve an era-appropriate bugsnag-php.
- Which Symfony and PHP versions does this package support?
- It targets Symfony2 era applications, roughly Symfony 2.3 through 2.8, on PHP 5.x and early 7.x. Those frameworks and PHP branches are end-of-life and no longer receive security patches. Running it in production means inheriting that unsupported runtime exposure alongside the package's own lack of maintenance.
- How do I configure the Bugsnag API key and release stage in this bundle?
- Both are set through the bundle's configuration section in your Symfony config files, typically app/config/config.yml, rather than through environment-driven config publishing. You provide the API key and the release stage value that should be attached to reported events. Because there is no Laravel config publishing workflow, none of this transfers to a Laravel project.
- How does the bundle report uncaught exceptions automatically?
- It registers a kernel event listener on the exception event, so any exception that reaches Symfony's kernel is forwarded to the Bugsnag PHP notifier. That is the same responsibility Laravel's exception handler report method covers in a Laravel app. Because the listener sits on the global exception path, a wiring problem can fail silently rather than throwing an obvious error.
- Can I attach custom metadata and user context to reported errors?
- Yes, the bundle exposes the notifier as a container service, so you can inject it and add custom metadata or user context before an error is reported. In a Laravel application the equivalent is the Bugsnag client bound in the container by bugsnag/bugsnag-laravel. Be deliberate about what you attach, since user identifiers and request data are a data-egress and PII concern.
- Is simpleweb/bugsnag-bundle actively maintained and safe for production?
- No. It has a single star, no dependents, and a very low maturity score, which means no peer review and no downstream bug surface. It also pins a generation of bugsnag-php that drifts from current Bugsnag API conventions around event payloads, release tracking, and filtering. Treat it as a reference implementation, not a dependency.
- Can I make this Symfony bundle run inside Laravel with a custom service provider?
- Technically you could write a service provider, a container binding, and an exception handler integration, but that means rebuilding exactly what bugsnag/bugsnag-laravel already provides. There is no scenario where that custom glue is cheaper or safer than adopting the official SDK. If an unstated constraint like a frozen Composer set or an internal fork is driving this, resolve that constraint first.
- How do I verify that errors are actually being reported to Bugsnag?
- Trigger a deliberate exception in a non-production environment and confirm the event appears in your Bugsnag dashboard with the expected release stage and context. Do this as an automated smoke check, because the most dangerous failure mode of an unmaintained exception listener is silently delivering zero events while everything looks healthy. Also confirm your filtering rules so sensitive fields are not sent.
Weaver
How can I help you explore Laravel packages today?