Weave Code
Guzzle Bundle Laravel Package
freshcells/guzzle-bundle
A Symfony bundle that integrates the Guzzle HTTP client into your application, offering service configuration and dependency injection so you can make and manage outgoing HTTP requests cleanly within Symfony projects.
A bundle integrating Guzzle >=4.0 in Symfony
Frequently asked questions about Guzzle Bundle
- Can I use freshcells/guzzle-bundle in a Laravel application?
- No. freshcells/guzzle-bundle is a Symfony Bundle, not a Laravel package. It relies on Symfony Kernel bundle registration, a DependencyInjection extension, and a configuration tree that Laravel does not provide. Making it work would require pulling symfony/framework-bundle into Laravel, which introduces a second container and configuration system for a single HTTP client concern. Use Laravel's built-in Http facade instead.
- How do I install freshcells/guzzle-bundle?
- Installation is Symfony-specific: require the package with Composer, register the bundle in your Symfony Kernel or config/bundles.php, and define Guzzle clients through the bundle's YAML configuration. There is no Laravel service provider or auto-discovery path. For Laravel, install Guzzle directly if needed or use the framework's Http facade, which is already Guzzle-backed.
- What Laravel version is supported by freshcells/guzzle-bundle?
- None. The package has no Laravel support matrix because it is a Symfony Bundle and does not ship a Laravel service provider, facade, or publishable config. Laravel 7 and later already include the Illuminate\Support\Facades\Http client with fakes, retries, and pooling. Standardize on that first-party abstraction rather than adding a Symfony bundle.
- How does freshcells/guzzle-bundle compare to Laravel's Http facade?
- Laravel's Http facade is first-party, Guzzle 7-backed, and integrated with testing via Http::fake(), retries, backoff, and request pooling. freshcells/guzzle-bundle is a thin Symfony DI wrapper that reads YAML configuration and registers configured Guzzle clients as container services. For Laravel, the facade provides more capability with no third-party bundle or extra architecture. The bundle is not a replacement for Laravel's HTTP client.
- Is freshcells/guzzle-bundle maintained and safe for production?
- Treat it as high risk. It has zero stars and zero dependents, it is a fork of the archived Csa GuzzleBundle, and there is no evidence of CI, a security policy, issue triage, or a release cadence. Its Guzzle constraint of >=6.0 admits Guzzle 6, which reached end-of-life in 2019 and no longer receives security patches. No downstream production usage has validated this fork.
- What Guzzle versions does freshcells/guzzle-bundle support?
- The Composer constraint is GuzzleHttp >=6.0, which permits Guzzle 6 even though that major reached end-of-life in 2019. There is no clear signal that the floor has been raised to exclude EOL majors or that Guzzle 7 is the supported target. A permissive lower bound means a resolver can legitimately pin a vulnerable version. Laravel's Http facade already uses a maintained Guzzle release underneath.
- How do I configure Guzzle clients with freshcells/guzzle-bundle?
- In Symfony, the bundle reads its configuration tree and registers configured Guzzle clients as container services, typically through YAML. Laravel has no equivalent bundle extension or config tree, so there is no supported configuration path in a Laravel app. For Laravel, configure Guzzle manually in a service provider or use the Http facade with its own options.
- How do I test HTTP requests if I use freshcells/guzzle-bundle?
- The bundle does not add testing helpers; in Symfony you would mock or replace the underlying Guzzle handler yourself. In Laravel, the correct approach is Http::fake(), which is built into the framework's HTTP client and requires no third-party bundle. That testing ergonomics is one reason to prefer Laravel's first-party Http facade over this Symfony bundle.
- What are alternatives to freshcells/guzzle-bundle for Laravel?
- For Laravel, use the Illuminate\Support\Facades\Http client, which is Guzzle-backed and supports fakes, retries, and concurrency. If you need direct Guzzle access, bind a configured Guzzle client in a Laravel service provider instead of installing a Symfony bundle. symfony/http-client is a valid alternative only in Symfony projects, not Laravel.
- Does freshcells/guzzle-bundle work with Laravel's service container or dependency injection?
- No. The package depends on Symfony's DependencyInjection extension and compiler pass pipeline, and it activates only when a Symfony Kernel boots the bundle. Laravel's service container does not understand Symfony bundle registration or the bundle's configuration tree. In Laravel, bind Guzzle clients through a service provider or use the Http facade.
Weaver
How can I help you explore Laravel packages today?