- Is simonberger/buzz-bundle compatible with Laravel?
- No. It is a Symfony bundle that registers Buzz clients in the Symfony service container, so it has no Laravel service provider, facade, or configuration integration. Laravel applications should use the framework's built-in HTTP client, which provides dependency injection, testing fakes, and retries without adding a legacy Symfony dependency.
- How do I install simonberger/buzz-bundle?
- You would normally install it with Composer using composer require simonberger/buzz-bundle, then register the bundle in your Symfony kernel and add a buzz configuration block. However, the repository is archived and its constraints likely target older Symfony and PHP versions, so installation on a current Symfony 6 or 7 or Laravel stack will usually fail dependency resolution. Treat any successful install as a warning sign and inspect the resolved versions carefully.
- What Symfony versions does this Buzz bundle support?
- The bundle predates modern Symfony HTTP abstractions and was built for older Symfony releases that used bundle extension aliases, Configuration trees, and ContainerAware-style patterns. Those conventions changed or were removed across Symfony 5 and 6, so the package is unlikely to resolve on Symfony 6 or 7 without a fork. For any current LTS, use symfony/http-client instead.
- Is simonberger/buzz-bundle maintained or safe for production?
- No. The repository is archived, has zero stars and zero dependents, and has no active maintainer, security advisory feed, or CVE triage process. Any vulnerability in the bundle or its transitive Buzz dependencies becomes your incident, with no upstream fix expected. Production use would require owning a fork and a security patch cadence.
- What is the Buzz HTTP client and is it still relevant?
- Buzz is Kris Wallsmith's lightweight HTTP client library, and this bundle's only job is to wire Buzz clients and middleware into Symfony's container. Buzz is a legacy lineage compared with Guzzle and symfony/http-client, and PSR-7 and PSR-18 alignment plus TLS, proxy, and timeout semantics may differ from platform defaults. Modern Symfony and Laravel applications have first-party HTTP clients that cover the same use cases.
- What should I use instead of BuzzBundle in Laravel?
- Use Laravel's built-in HTTP client, which is built on Guzzle and provides a fluent API, dependency injection, retries, and Http::fake() for tests. If you need PSR-18 interoperability, Guzzle is a maintained choice that Laravel already depends on. Neither requires a Symfony bundle or the legacy Buzz API.
- What should I use instead of BuzzBundle in Symfony?
- Use symfony/http-client with autowired HttpClientInterface, scoped clients per integration, MockHttpClient for tests, retry and backoff, streaming, and profiler integration. If existing code requires a Buzz-shaped call API, put an internal transport interface in front of the client and implement it against symfony/http-client. That contains the legacy surface and makes the transport swappable.
- Can I mock or test HTTP calls made through this bundle?
- The bundle registers Buzz clients as container services, so in principle you can replace a service with a mock in the test container. In practice the archived state means no maintained test integration for current Symfony versions, and Buzz's mocking approach is not the same as MockHttpClient or Laravel's Http::fake(). For reliable tests, prefer a first-party client with built-in fakes.
- Does BuzzBundle support PSR-18 or PSR-7 HTTP interfaces?
- Not reliably. Buzz is an older HTTP client lineage, and its PSR-7 and PSR-18 alignment may diverge from what modern applications and frameworks expect. If PSR-18 interchangeability is a requirement, choose Guzzle or symfony/http-client, both of which have maintained PSR-18 adapters and clear upgrade paths.
- Why was simonberger/buzz-bundle archived, and can I fork it?
- It was archived because Symfony added symfony/http-client as a first-class abstraction, making a third-party bundle that only configures a client redundant, and the package has no maintainer or dependents. You can fork it, but you would own Symfony 6 and 7 compatibility, PHP 8.2+ updates, security patches, and a removal plan. For most teams, replacing the intent with symfony/http-client or Laravel's HTTP client is cheaper than maintaining the fork.