Weave Code
Raygun Bundle Laravel Package
onceit/raygun-bundle
A Symfony bundle that integrates Raygun error tracking into your application. It captures exceptions and sends detailed reports to Raygun, with configurable settings to help you monitor and debug production issues quickly.
Symfony2 Raygun Bundle
Frequently asked questions about Raygun Bundle
- Can I install onceit/raygun-bundle in a Laravel application?
- No. onceit/raygun-bundle is a Symfony2 bundle that extends Bundle and relies on DependencyInjection extensions, Resources/config/services.yml, and a kernel.exception listener, none of which exist in Laravel. Its symfony/framework-bundle ~2.x constraint also hard-conflicts with the Symfony components Laravel ships, so Composer will not resolve it alongside a modern Laravel app. Making it work would require a fork-and-rewrite, which costs more than writing a small adapter from scratch.
- What does onceit/raygun-bundle actually do?
- It wires the framework-agnostic raygun4php SDK into a Symfony2 application so uncaught exceptions are captured and sent to Raygun as detailed reports. Configuration lives in the bundle's DI extension and services.yml, and a kernel.exception listener forwards exceptions to the client. For Laravel, only the underlying idea is transferable: register raygun4php and call it from the exception pipeline.
- Is onceit/raygun-bundle still maintained?
- No. Last activity predates Symfony2's end of life in 2018, and there are no tagged releases, no security response process, and no CVE triage. Adoption signals are effectively zero: 0 stars, 0 dependents, and a score of 0.03, so no production bug surface has ever been exercised. Treat it as abandoned prior art rather than a dependency.
- Does onceit/raygun-bundle support Laravel 10 or Laravel 11?
- No. It targets Symfony2 only and pins symfony/framework-bundle to ~2.x, which is incompatible with the Symfony ^6/^7 components Laravel uses. Laravel 11 also changed the exception handler contract around report and render, so any inherited assumptions would need rework anyway. The package ships no service provider, facade, or publishable config for Laravel.
- How do I integrate Raygun error tracking into a Laravel app then?
- Write a thin first-party adapter over the framework-agnostic raygun4php SDK. Register the client as a singleton in a service provider, inject it into App\Exceptions\Handler::report() or a dedicated reporting listener, and add a Monolog handler for non-exception errors. Abstract it behind an ErrorReporter interface so Raygun can be swapped for Sentry or Bugsnag without touching call sites. This is roughly 100 lines of glue code.
- What are the best alternatives to onceit/raygun-bundle for Laravel error tracking?
- The Laravel-native options are sentry/sentry-laravel, Bugsnag, Rollbar, and Flare, all actively maintained with service providers and config out of the box. Raygun itself is still usable via raygun4php plus a small adapter. Raygun spans both crash reporting and APM/performance while the alternatives differ in strength, so match the tool to the requirement. Confirm the vendor decision before spending engineering time on any integration.
- How do I keep Raygun reporting from slowing down or breaking requests in Laravel?
- Never call the Raygun API synchronously on the request path; queue the report or dispatch it after the response is sent. Under Laravel Octane, do not bind the client as a long-lived singleton holding stale request state — resolve it per report or reset it per request. Configure sampling and quotas up front so an error storm cannot exhaust your plan. Roll out to staging first, then a production canary.
- Is onceit/raygun-bundle safe to use — license and supply chain?
- The license is the one clean element: MIT, permissive, and commercially compatible. The risk is supply chain, not licensing. Because the bundle is abandoned, its transitive Guzzle and PSR dependencies are a standing SCA finding, and nobody is available to triage CVEs or respond to disclosures. Raygun's own API has also moved on since this wrapper was written.
- How should I test and roll out a Raygun integration in a Laravel app?
- Because you own the adapter, bind a fake ErrorReporter in your test suite and assert that report() is called instead of hitting the network. For rollout, run a staging POC first (one to two days), then set sampling and quota limits, then a production canary. Follow with a 30-day review of cost and signal quality before deciding whether to keep the in-house adapter or migrate to an official package.
- Who owns the code if we fork onceit/raygun-bundle?
- Whoever forks it does, permanently: zero upstream means every patch, re-audit, and compatibility fix becomes your team's responsibility. That is a heavy ongoing liability for functionality that takes about a day to write fresh. The adapter approach caps the liability at a small, well-understood surface. Identify the long-term owner before any engineering spend is approved.
Weaver
How can I help you explore Laravel packages today?