- Can I install gremo/buzz-bundle in a Laravel application?
- No. It is a Symfony bundle, not a Laravel package, and Laravel has no bundle subsystem or auto-discovery path for it. There is no service provider or facade, and the container wiring it provides is inert in Laravel. Adopting it would mean forking and rewriting the integration layer.
- Does gremo/buzz-bundle support Laravel 10 or Laravel 11?
- No. The package targets Symfony 2.x-era applications and PHP 5.x-era code, with no Laravel version support. It is incompatible with modern PHP 8 runtimes due to removed functions and old string offset syntax. Laravel's native Http facade is the supported alternative.
- How do I install gremo/buzz-bundle?
- Historically you installed it with Composer and registered Gremo\BuzzBundle\GremoBuzzBundle in a Symfony AppKernel. On Symfony 4+ bundle-less applications that registration path does not exist, so you would maintain a hand-written services.yaml definition. In Laravel there is no supported install path.
- What is gremo/buzz-bundle used for?
- It is a thin Symfony dependency injection wrapper that configures and injects a Buzz\Browser HTTP client. It exposes container-level client and cURL options for legacy Symfony apps. It does not provide retries, middleware hooks, or PSR-18 interoperability.
- Is gremo/buzz-bundle maintained or abandoned?
- The upstream repository is archived and abandoned, with no security patching for roughly a decade. Adoption is minimal at about 7 stars and zero dependents, so there is no community to surface bugs. Any vulnerability becomes your responsibility to fix in a funded fork.
- What are the alternatives to gremo/buzz-bundle for Laravel?
- Use Laravel's native Http facade, which is Guzzle-backed, with Http::withOptions() and Http::retry(). For PSR-7 or PSR-18 needs, use Guzzle or another modern client. On Symfony, symfony/http-client is the modern replacement; Buzz itself is superseded and pre-PSR-7.
- Is the Buzz HTTP client PSR-7 or PSR-18 compatible?
- No. Buzz message objects such as Buzz\Message\Request and Buzz\Message\Response predate PSR-7. They do not interoperate with modern middleware, PSR-18 clients, or Laravel's HTTP client abstraction. That blocks integration with most current tooling.
- Will gremo/buzz-bundle work on PHP 8?
- Almost certainly not. The code is PHP 5.x-era and uses patterns incompatible with PHP 8, including removed functions and old string offset syntax. There is no evidence it has ever run on a modern runtime, and pinning its old constraints will collide with modern symfony packages.
- How do I test HTTP calls if I previously used gremo/buzz-bundle?
- You cannot rely on the bundle's container wiring in Laravel. Introduce a narrow internal interface around outgoing calls and fake it in tests, then migrate legacy Browser::get, post, and submit call sites to that seam. For new Laravel code, use Http::fake() with the Http facade, which is testable and supported.
- Should I use gremo/buzz-bundle in production?
- No. For a Laravel target it is not applicable, and for legacy Symfony it is a high, mostly unrecoverable risk. The bundle is abandoned, the transitive Buzz client is dead, and there is no security patching. Replace it with a framework-native client rather than integrating it.