Weave Code
Guzzle Bundle Laravel Package
mapudo/guzzle-bundle
Symfony bundle that integrates the Guzzle HTTP client, providing a configurable service for making HTTP requests, with profiling and easy dependency injection into your applications.
The Mapudo GuzzleBundle allows integrating Guzzle into Symfony projects.
Frequently asked questions about Guzzle Bundle
- Is mapudo/guzzle-bundle compatible with Laravel?
- No. mapudo/guzzle-bundle is a Symfony bundle that registers clients through a DependencyInjection extension and YAML configuration. Laravel loads service providers rather than bundles, so there is no registration entry point in a Laravel app. You would have to rewrite the package's wiring before it could run under Laravel.
- How do I install mapudo/guzzle-bundle?
- In a Symfony project you would install it with composer require mapudo/guzzle-bundle, enable it in bundles.php, and configure clients under the bundle's config key. In Laravel there is no bundle registration step, so installation alone will not give you usable services. Check constraints first: the last release, v2.3.0, was published on 12 April 2019 and is presumed to pin Guzzle 6-era, PSR-7 1.x, PHP 7.x and Symfony 3/4.
- What Laravel version does mapudo/guzzle-bundle support?
- None officially. It is a Symfony bundle and does not ship a Laravel service provider or facade, so no Laravel version is supported. The registration model is Symfony-only, which means Laravel 10 or 11 cannot load it without custom glue code.
- What is the Laravel alternative to mapudo/guzzle-bundle?
- Use Laravel's built-in HTTP client, which wraps Guzzle and is configured through config/services.php. Named clients, middleware and logging channels are first-class Laravel primitives, so you do not need a bundle. For per-upstream settings, define them in config/services.php and attach middleware with Http::withMiddleware or a Guzzle handler stack.
- Can I use mapudo/guzzle-bundle with Guzzle 7 and PHP 8?
- Almost certainly not, but treat it as unverified until you run a Composer constraint check. A 2019-era manifest will very likely require Guzzle 6, PSR-7 1.x, PHP 7.x and Symfony 3/4, none of which fit a modern PHP 8 and Laravel 10/11 estate. The v2.3.0 release notes say nothing about widening dependencies. Confirm with composer why-not only if someone actually proposes adoption.
- How do I configure multiple Guzzle clients with mapudo/guzzle-bundle?
- The bundle lets you declare one or many named Guzzle clients in configuration and inject them by service id, so shared base URLs, timeouts and handlers stay centralized. That is a Symfony container pattern; the same result in Laravel comes from binding configured GuzzleHttp\Client instances in a service provider or config/services.php. Do not expect the bundle's YAML to be read by Laravel.
- What does the v2.3.0 channel-scoped logger feature do?
- v2.3.0, published 12 April 2019, added channel-scoped logger injection to the bundle's LogMiddleware. It is a configuration convenience inside the bundle's own middleware stack, not a portability or dependency change. The term channels is Monolog terminology and existed in both Symfony and Laravel at the time; nothing in the release indicates Laravel targeting. In Laravel you already get this with logging channel configuration and middleware.
- Is mapudo/guzzle-bundle maintained or safe for production?
- Treat it as unmaintained. There have been zero releases since April 2019, which is a long gap for a security-sensitive HTTP egress layer. Stars and dependents show no community forcing function, and the release notes give no maintenance commitment. For production Laravel work, use the framework HTTP client instead.
- How do I test HTTP clients configured by mapudo/guzzle-bundle?
- The package does not document a testing layer, so in Symfony you would normally replace configured client services with mocks in the container. In Laravel, use Http::fake to stub responses and assert requests against the framework HTTP client. If you are evaluating a bridge, test the bridge wiring itself rather than the bundle, since the Symfony container is not loaded.
- Should I use mapudo/guzzle-bundle in a mixed Symfony and Laravel application?
- Only if a Symfony service already depends on it and that service is pinned and isolated from the Laravel application. Do not introduce it into Laravel as a new dependency: the bypass path using native Guzzle clients or Laravel's HTTP client is simpler and supported. The v2.3.0 logging change does not make a bridge cheaper, because you would still have to replicate the behaviour.
Weaver
How can I help you explore Laravel packages today?