- Can I use m6web/guzzle-http-bundle in a Laravel application?
- Not directly. It is a Symfony HTTP Kernel bundle built around a Bundle subclass, a DependencyInjection extension that parses the guzzle_http config tree, and compiler passes that register clients in the Symfony container. Laravel has no bundle lifecycle or config-tree loader, so you would have to reimplement its bootstrap in a service provider, which defeats the purpose. The practical recommendation is to use Laravel's Http facade or a small Guzzle client factory instead.
- Does m6web/guzzle-http-bundle support Laravel 10, 11 or 12?
- No. The package targets Symfony and has no Laravel service provider, facade, or version constraints for laravel/framework. Composer may still resolve it because it is MIT, PSR-4 and PHP-only, but resolving is not the same as integrating. There is no supported Laravel version matrix, and the maintainers have no obligation to preserve Laravel-adjacent use cases.
- What does m6web/guzzle-http-bundle actually do?
- It lets Symfony applications declare multiple named Guzzle clients in bundle configuration and registers each one as a container service. It also adds logging, configurable handlers and middleware, and a Symfony profiler data collector so you can inspect outgoing requests and responses. Its real value is Symfony-idiomatic configuration, not HTTP capability — that part is Guzzle itself.
- How do I install m6web/guzzle-http-bundle?
- You would run composer require m6web/guzzle-http-bundle and enable the bundle in your Symfony kernel, then add a guzzle_http configuration block. That registration step is Symfony-specific and does not exist in Laravel, where packages are discovered through service providers. For a Laravel app, installation is not recommended because the bundle's entry points are all Symfony extension points.
- Is m6web/guzzle-http-bundle actively maintained and safe for production?
- It has recent tagged releases, but the project has roughly 17 GitHub stars and zero dependents, and it is maintained for BedrockStreaming's own Symfony services. That is effectively a bus factor of one, with no visible production validation outside the vendor. The code surface is small and unlikely to be dangerous, but the dependency risk is moderate and the exit cost is yours to own.
- How do I configure multiple named Guzzle clients in Laravel?
- Use a config file such as config/http_clients.php with per-client base URI, timeout, headers and auth, then bind a small GuzzleClientFactory as a singleton in AppServiceProvider. Alternatively, use the Http facade with per-service configuration in config/services.php, plus retry(), withMiddleware() and Http::pool() for concurrency. Either approach is roughly 40 to 80 lines of code you fully own, with no Symfony coupling.
- What is the Laravel alternative to m6web/guzzle-http-bundle?
- Laravel already ships Guzzle through laravel/framework and wraps it in the Http facade, which covers named clients, timeouts, retries, middleware and pooling. For logging and observability, use Laravel middleware, events, or a maintained package rather than a Symfony profiler collector. If you like the bundle's per-client config schema, port that shape into a Laravel config array and map it onto Guzzle's client options.
- Does m6web/guzzle-http-bundle integrate with Laravel Telescope or Debugbar?
- No. Its inspection feature is a Symfony profiler data collector wired into the Symfony web profiler, and there is no equivalent hook for Telescope or Debugbar. Laravel's own HTTP client events and middleware are a better place to capture request and response data for those tools. Using the bundle would mean writing that integration yourself.
- Will m6web/guzzle-http-bundle conflict with the Guzzle version Laravel requires?
- Potentially yes. The bundle pins a Guzzle major version, and laravel/framework already requires its own Guzzle constraint, so the two can collide during Composer resolution. You should check the bundle's composer.json against your installed laravel/framework version before adding it. In most cases this constraint mismatch is another reason to skip the dependency.
- How do I test HTTP clients configured like m6web/guzzle-http-bundle in Laravel?
- The bundle ships no Laravel testing helpers, so you would test the underlying Guzzle clients directly with Guzzle's MockHandler and history middleware. If you follow the recommended Laravel path, Http::fake() and Http::assertSent() cover the same ground with far less setup. Either way, keep client construction in a factory so tests can inject a mock handler.