- Is juliendidier/buzz-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle. It registers Buzz Browser services and listener configuration into the Symfony dependency injection container, and it does not ship a Laravel service provider, facade, or config file. In a Laravel application there is nothing that consumes its Bundle class or DI extension.
- Can I install juliendidier/buzz-bundle in a Laravel application?
- You technically can add it to Composer, but it will not integrate with Laravel's container or HTTP stack. Making it functional would require pulling Symfony framework, http-kernel, config, and dependency-injection packages into a Laravel app just to host an HTTP client wrapper. That is a large dependency surface for a client Laravel already provides natively.
- Does buzz-bundle support Laravel 10 or Laravel 11?
- No. The package targets Symfony, not Laravel, so it does not declare Laravel 10 or Laravel 11 support and has no Laravel service provider. Laravel version compatibility is not the right question for this package, because it never enters Laravel's bootstrapping path.
- How do I make outbound HTTP requests in Laravel without BuzzBundle?
- Use Laravel's native HTTP client via the Http facade. Http::get(), Http::post(), timeout(), retry(), Http::pool(), and Http::fake() cover the common outbound request, retry, concurrency, and testing needs. It is built on Guzzle and is actively maintained with the framework.
- Is the Buzz HTTP client still maintained or end-of-life?
- Buzz, the underlying client this bundle wraps, is effectively end-of-life and has been superseded by symfony/http-client and Guzzle. Older Buzz releases predate PSR-18 and use proprietary message classes, which adds lock-in. Adopting it means taking on a client without an active security response path.
- How do I inject or autowire a Buzz Browser service in Laravel?
- You cannot autowire the bundle's Buzz Browser services in Laravel because they are registered by a Symfony DI extension, not a Laravel service provider. If you genuinely need Buzz, bind a client instance manually in a service provider and inject it behind an application-owned interface. Prefer binding an HTTP client contract you control so the underlying implementation can be swapped later.
- How do I test HTTP calls if I use BuzzBundle in Laravel?
- BuzzBundle has no Laravel testing integration, so Http::fake() and Laravel's assertion helpers will not intercept Buzz requests. You would have to mock Buzz classes yourself or use a generic HTTP mocking layer. With Laravel's native Http facade, Http::fake() gives you request recording and response stubbing out of the box.
- Does juliendidier/buzz-bundle support PSR-18 or PSR-7?
- The bundle wraps Buzz, and older Buzz versions predate PSR-18 and use their own message classes rather than PSR-7 or PSR-18 interfaces. The bundle itself does not add a PSR-18 layer. If PSR-18 interoperability matters, use Guzzle, symfony/http-client, or Laravel's Http client instead.
- What are the best alternatives to buzz-bundle for Laravel HTTP clients?
- For Laravel applications the best alternative is the built-in Http facade over Guzzle, because it provides retries, pooling, fakes, middleware, and typed error handling without extra container baggage. If you need a framework-agnostic contract, depend on PSR-18 or Guzzle's ClientInterface and bind it in a service provider. On Symfony estates, symfony/http-client is the current first-party answer.
- Is buzz-bundle safe to use in production for a Laravel app?
- It is not a good production choice for Laravel: it is a single-maintainer Symfony bundle with no Laravel integration and it wraps an end-of-life HTTP client. The main risks are the abandoned dependency chain, legacy service-definition formats that may fail modern dependency resolution, and no clear security response path. Use Laravel's native HTTP client instead, and keep any Buzz-specific adapter quarantined behind an owned interface if you truly must.