- Does m6web/wsclient-bundle work with Laravel?
- No. m6web/wsclient-bundle is a Symfony bundle, and its value comes from Symfony's Kernel, DependencyInjection extension, semantic configuration tree, and service-container compilation. Laravel has no bundle lifecycle, compiler passes, or Configuration tree, so the package's service wiring is inert in a Laravel app. Laravel's PSR-11 compatible container does not execute Symfony compiler passes. Treat it as a design reference, not an installable Laravel dependency.
- Can I install m6web/wsclient-bundle in a Laravel project with Composer?
- Composer may resolve the package, but it will not be registered or bootstrapped the way Laravel expects. There is no Laravel service provider, no config publishing, and no facade or auto-discovery entry, so nothing is wired into the container. Getting it to run would mean pulling in a partial Symfony container or reimplementing the config-to-client mapping yourself. The realistic options are a port or a rewrite, not an integration.
- Which Laravel versions does m6web/wsclient-bundle support?
- There is no Laravel compatibility matrix for this package. It is a Symfony bundle with a Symfony 2.x-era dependency floor and a pre-PSR-18 Guzzle requirement, and v5.4.1 did not publish modern PHP or framework constraints. Before making any decision, check the composer.json constraint floor yourself, since that is the fact most likely to change the assessment. The absence of a stated Laravel support policy is itself the answer for Laravel teams.
- What should I use instead of m6web/wsclient-bundle in Laravel?
- For HTTP-style calls, Laravel's Illuminate\Support\Facades\Http facade, backed by Guzzle 7, already provides retry, timeout, middleware, fakes, and testing hooks. For actual WebSocket client connections, pair a maintained PHP WebSocket client with a small Laravel service provider that binds configured connections as singletons. That combination covers the same use cases without carrying Symfony-era abstractions. It also keeps you on a supported transport stack.
- How do I configure multiple WebSocket client connections in Laravel?
- Express each endpoint definition, including base URL, auth, headers, timeouts, and retry policy, in a Laravel config file. Then bind a small factory as a singleton that maps those config entries to client instances and inject it where needed. The evaluation estimates roughly 150 lines of Laravel config plus a small factory to replace the bundle's declarative endpoint configuration. That is far less work than adapting the bundle's container wiring.
- Is m6web/wsclient-bundle maintained and safe for production?
- The technical risk is rated high. Version 5.4.1 is a retrocompatibility patch that restores previously removed methods on ResponseAdapterInterface, which shows the interface contract is churning without a stability guarantee. It does not modernize the dependency floor, add CI, publish a compatibility matrix, or establish a security advisory channel. The transitive HTTP stack is unchanged, so a low-activity dependency with an EOL transport should be checked against your security policy.
- What changed in m6web/wsclient-bundle v5.4.1?
- v5.4.1 touches ResponseAdapterInterface, an internal transport abstraction, restoring methods that had been removed in the preceding release. It does not add framework-agnostic packaging, PSR-18 alignment, or a Laravel service provider. The patch mainly corrects the record that the package is not fully inert, since a maintainer did ship a release. A retrocompatibility fix is still the weakest possible maintenance signal.
- Can I reuse the bundle's config-driven client pattern in Laravel?
- Yes, as a design reference rather than a dependency. The useful idea is a registry that maps declarative connection config to lazily built client services. In Laravel you would re-express that with mergeConfigFrom, a published config file, and a factory bound as a singleton. The evaluation recommends exactly this reimplementation path instead of porting the bundle.
- How do I replicate the bundle's event dispatching and logging in Laravel?
- Laravel's event dispatcher and Log facade cover the same ground the bundle gets from Symfony's dispatcher and logger integration. Dispatch domain events around connect, send, receive, and failure paths, and log through the framework's channels instead of a bundle-specific handler. This is straightforward application code and does not require any Symfony component. It also keeps observability consistent with the rest of your Laravel services.
- How much work is porting m6web/wsclient-bundle to Laravel versus rewriting it?
- The evaluation says reimplement, do not port. Start by inventorying the endpoint definitions you actually need, including base URLs, auth, headers, timeouts, and retry policy, then express them in Laravel config with a client factory. Migration cost from Symfony 2 idioms to Laravel idioms should be compared against a clean rewrite, and the rewrite is expected to come in well under a week. Confirm whether any existing service already consumes the bundle so you understand the blast radius before replacing it.