Weave Code
Symfony Messenger Bundle Laravel Package
macpaw/symfony-messenger-bundle
MacPaw's Symfony Messenger bundle streamlines integrating Symfony Messenger into PHP applications, with configuration for transports, message buses, handlers, and worker commands so you can dispatch messages and process background jobs asynchronously with minimal boilerplate.
A Symfony bundle to extend Symfony Messenger Component
Frequently asked questions about Symfony Messenger Bundle
- How do I install macpaw/symfony-messenger-bundle in a Laravel app?
- You can install it with Composer, but it is a Symfony bundle rather than a Laravel package. Laravel will not auto-register a ServiceProvider or publish config for it. In a pure Laravel app you would need to bootstrap Symfony Kernel and FrameworkBundle mechanics yourself or integrate symfony/messenger directly.
- Does macpaw/symfony-messenger-bundle support Laravel 10 or Laravel 11?
- The package does not declare Laravel support and is built for Symfony bundle conventions. Laravel 10 and 11 include Symfony components, but they do not provide the FrameworkBundle and Kernel bundle registration this package expects. Its actual constraints depend on symfony/messenger and doctrine/orm ranges that are not clearly stated. Treat it as unsupported in Laravel until you verify Composer resolution and runtime behavior yourself.
- What does macpaw/symfony-messenger-bundle add over symfony/messenger?
- It provides preconfigured Messenger service definitions and defaults, simple handler and middleware registration, transport configuration, and Symfony console integration for consuming messages. The technical evaluation argues these are thin conveniences over first-party symfony/messenger middleware. It also asks whether the bundle justifies the doctrine/orm 3 pin that v1.1.0 introduces.
- Can I use Symfony Messenger instead of Laravel queues?
- Technically yes, but Messenger is a separate async subsystem from Laravel queues. It uses envelopes, stamps, middleware ordering, sender and receiver transports, its own worker loop, failure transport, and messenger:failed:retry. Laravel already gives you queue:work, Horizon, failed_jobs, retries, and job middleware. Do not adopt this bundle just to replace Laravel queues; choose one boundary and stay behind it.
- How do I configure transports and message handlers with this bundle?
- Configuration follows Symfony bundle conventions through service definitions and bundle config, with transports for async processing and registration for handlers and middleware. There is no publishable Laravel config file, and every middleware still has to be hand-instantiated into a Messenger bus you build and supervise. Exact options are not well documented in the provided material, so inspect the bundle source before relying on it.
- Is macpaw/symfony-messenger-bundle production-ready?
- The available signals are not reassuring: 2 stars, zero dependents, a single publisher, a two-line changelog, and no test or CI signal. The package does not state supported Symfony, doctrine/orm, or PHP ranges, nor does it state a production maintenance commitment. v1.1.0 also shipped a major doctrine/orm 3.x bump inside a minor release. For a Laravel-first codebase, the risk is high and the architecture fit is poor.
- Why does v1.1.0 require doctrine/orm 3.x and is that a breaking change?
- The bundle includes a Doctrine transport, and v1.1.0 upgrades doctrine/orm to 3.x, so that pin becomes part of your dependency resolution surface. Doctrine ORM 3 is genuinely breaking versus 2.x, with annotation driver removal, EntityManager and metadata API changes, and dropped legacy mapping support. If any part of your estate still runs Doctrine 2, coexistence becomes materially harder. Shipping this major bump in a minor version is a semver-discipline failure.
- What are alternatives to macpaw/symfony-messenger-bundle for async jobs in Laravel?
- For Laravel async work, use Laravel queues with queue:work or Horizon, job middleware, failed_jobs, retries, and your existing monitoring. If you are already committed to Symfony Messenger, use first-party symfony/messenger middleware or a small custom Messenger middleware instead of adding this bundle. The bundle is reasonable only where symfony/messenger is already a platform commitment.
- How do I test messages and handlers if I adopt this bundle?
- The package provides no visible test suite or CI signal, so you must own the testing and failure semantics yourself. With Messenger you would typically use in-memory transports and bus assertions, but this bundle does not document its testing approach. Verify retry, failure transport, and handler behavior in a staging environment before production.
- Is macpaw/symfony-messenger-bundle actively maintained and can I trust its version numbers?
- The package has 2 stars, zero dependents, and a single publisher, and its PR references an internal tracker key, suggesting internal glue rather than an externally driven roadmap. The changelog is two lines with no migration notes. A PR titled Release 2.0 shipped as tag v1.1.0 with a major doctrine/orm bump, so you cannot infer breaking-change risk from the version number. Treat every bump as potentially breaking.
Weaver
How can I help you explore Laravel packages today?