Weave Code
Bugsnag Laravel Package
styleci/bugsnag
StyleCI's Bugsnag package integrates the Bugsnag error monitoring service into Laravel applications, wiring exception reporting and crash notifications into the framework's handler and configuration for straightforward setup.
[DEPRECATED] A Bugsnag wrapper for Laravel 5
Frequently asked questions about Bugsnag
- How do I install styleci/bugsnag in a Laravel 5 application?
- Install it with Composer by running composer require styleci/bugsnag from the root of your Laravel 5 project. On Laravel 5.5 and later the service provider can be picked up by package auto-discovery, while earlier 5.x releases require you to register the provider in config/app.php manually. Once installed, supply your Bugsnag API key through the package configuration so the bridge can authenticate with the service.
- Does styleci/bugsnag work with Laravel 6, 7, 8, or newer versions?
- The package is described as a Bugsnag bridge specifically for Laravel 5, so it is not advertised as compatible with Laravel 6 and beyond. For newer framework releases you should use the official bugsnag/bugsnag-laravel SDK, which tracks current Laravel versions. Forcing this bridge into a modern Laravel app risks conflicts with the framework's exception handler and its contracts.
- Where do I put my Bugsnag API key when using this package?
- The bridge reads its credentials from the package configuration, so you publish or create that config file and set your Bugsnag API key there. A common pattern is to keep the key in your .env file and reference it from the config array so secrets stay out of version control. Without a valid key, exception reports will never reach your Bugsnag dashboard.
- How does styleci/bugsnag hook into Laravel's exception handler?
- The bridge wires Bugsnag reporting into the framework's exception handler, so exceptions that reach the handler are forwarded to Bugsnag as crash notifications. You keep using Laravel's normal reporting flow instead of calling the Bugsnag client manually in every controller. The integration's options live in the package config published into your application.
- Is styleci/bugsnag still maintained, or should I switch to bugsnag/bugsnag-laravel?
- The repository sits under a deprecated namespace and targets Laravel 5, which is long past end of life, so treat it as a legacy dependency. For any actively maintained project the official bugsnag/bugsnag-laravel package is the supported path. If you are pinned to Laravel 5 the bridge can still work, but plan a migration rather than building new features on it.
- How do I disable Bugsnag reporting in local development with this package?
- Control this through the package config or environment, enabling reporting only when the API key or an explicit enabled flag is present. If your local .env has no Bugsnag key, the bridge has nothing to report to and errors stay in your logs. Many teams also skip reporting when APP_DEBUG is true so local stack traces do not pollute the shared dashboard.
- How can I test that styleci/bugsnag is actually reporting errors?
- Add a temporary route or a tinker command that throws an exception, then confirm the crash shows up in your Bugsnag dashboard within a minute or two. Because the bridge reports through Laravel's handler, a deliberately thrown exception is the simplest end-to-end check. Delete the test route afterwards and verify the report's release stage matches the environment you expected.
- Do I need to publish a config file to use styleci/bugsnag?
- The package ships a configuration file that you publish into your app's config directory so you can set the API key and adjust reporting options. Publishing is the recommended approach because it keeps your credentials out of the vendor directory and lets you version the settings you care about. In production, run php artisan config:cache after editing so the new values are picked up.
- What performance overhead does styleci/bugsnag add in production?
- On successful requests the bridge only costs the service provider registration, so normal traffic sees no meaningful overhead. Work happens when an exception reaches Laravel's handler and a report is sent to Bugsnag. That delivery is a network call, so a large burst of errors can add latency; filter or rate-limit noisy exceptions if that becomes a problem.
- Can I filter which exceptions get sent to Bugsnag?
- Filtering is normally handled through the package config, where you can ignore specific exception classes before the bridge forwards anything to Bugsnag. Laravel's own $dontReport list on the exception handler is the other lever, since the bridge reports what the handler reports. Combining both keeps validation errors and expected 404s out of your Bugsnag inbox.
Weaver
How can I help you explore Laravel packages today?