Weave Code
Catchable Bundle Laravel Package
forci/catchable-bundle
Symfony bundle for Forci Catchable that brings catchable exception handling to PHP applications. It integrates with Symfony’s error and exception workflow, helping centralize failure handling, reduce repetitive try/catch blocks, and keep controllers clean and consistent.
Forci Catchable Bundle
Frequently asked questions about Catchable Bundle
- Is forci/catchable-bundle a Laravel package?
- No. It is a Symfony bundle that hooks into Kernel::registerBundles(), a DependencyInjection extension, and Symfony's kernel.exception event, so it does not run under Laravel's service-provider bootstrapping or Illuminate\Foundation\Exceptions\Handler. A Laravel application cannot adopt it as shipped without porting the collector logic into a service provider and exception handler hook.
- How do I install forci/catchable-bundle in a Laravel app?
- You should not install it directly in a Laravel app. The package targets Symfony's bundle system, and a composer require is likely to fail or pull in Symfony 2.x or 3.x components that conflict with the Symfony 6.x and 7.x constraints required by Laravel 10 and 11. If you only want the pattern, read the source as a reference and build a small Laravel-native reporter instead.
- What does forci/catchable-bundle actually do?
- It converts PHP errors into catchable exceptions and routes them through Symfony's standard exception flow, with minimal bundle configuration and service wiring. That lets existing listeners, logging, and error responses handle failures consistently instead of relying on raw error handling. The value is the pattern of capturing unhandled errors close to where they are thrown, not a Laravel-ready component.
- Can I use forci/catchable-bundle with Laravel 10 or Laravel 11?
- Not without significant porting work. Laravel 10 and 11 require Symfony 6.x and 7.x components, while abandoned Symfony bundles of this type often pin older Symfony 2.x or 3.x dependencies, so Composer resolution is likely to fail or drag in a conflicting graph. Even if it installed, none of the bundle lifecycle would execute under Laravel.
- Is forci/catchable-bundle safe for production use?
- No, it is not a safe production dependency for a Laravel stack. The repository shows zero stars and zero dependents, no production validation, and no active maintenance, which is a serious concern for a package that touches every request and ingests stack traces and request payloads. The license is NOASSERTION, so there is no recognized grant to use, modify, or redistribute it.
- What license does forci/catchable-bundle use?
- The repository reports NOASSERTION, meaning there is no recognized open-source license grant. That is a legal stop rather than an engineering trade-off, because you lack clear permission to use, modify, or redistribute the code. The project is inactive enough that upstream clarification is unlikely, so treat it as reference-only and do not copy code without clarity.
- How does forci/catchable-bundle compare to Sentry for Laravel?
- Sentry, Flare, and Bugsnag already cover this scope with MIT or commercial licenses, large dependent counts, active security response, and first-class Laravel SDKs. Adoption is a service-provider registration and a config publish, often an afternoon including staging verification. forci/catchable-bundle offers no differentiated capability for Laravel and would require an owned port.
- How do I test error handling if I port the forci/catchable-bundle pattern?
- Test the Laravel-native replacement, not the Symfony bundle. Register a reportable() closure or a custom exception handler hook, then assert with feature tests that a thrown exception is reported once, contains the expected context, and does not leak credentials or PII. For queued reporting, use Queue::fake() and assert the job is dispatched, and keep a staging check against your real log channel.
- What are the best alternatives to forci/catchable-bundle for Laravel?
- Use Laravel's native report() and reportable() hooks for narrow cases, or adopt a maintained reporter such as sentry/sentry-laravel for broad observability. If you need to persist unhandled exceptions somewhere queryable, a handler override that dispatches a queued job to a dedicated table is roughly 100 lines of fully owned, testable code. Replace rather than port this bundle.
- Is forci/catchable-bundle maintained and should we add it to our roadmap?
- The adoption signals are consistent with an abandoned or never-adopted artifact: no stars, no dependents, no reported-issue history, and no named active maintainer visible in the context. A TPM should reject it as a direct dependency before any roadmap discussion. Route the observability requirement to a maintained solution or a small owned implementation and log the rejection.
Weaver
How can I help you explore Laravel packages today?