Weave Code
Simplebus Bundle Laravel Package
happyr/simplebus-bundle
Symfony bundle that integrates SimpleBus with the framework’s DI container, helping wire command, query, and event buses, register handlers and middleware, and use message buses in Symfony apps with minimal configuration.
At a glance
Frequently asked questions about Simplebus Bundle
- Is happyr/simplebus-bundle a Laravel package?
- No. It is a Symfony bundle built around a Bundle class, a DI Extension with a config tree, and compiler passes that auto-tag handler services. None of that maps onto Laravel's service container or package discovery. For Laravel, use the first-party Illuminate\Bus dispatcher instead.
- Can I install happyr/simplebus-bundle in a Laravel application?
- Composer may allow the install, but Laravel will not load or register a Symfony bundle. There is no service provider, facade, publishable config, or handler auto-discovery for Laravel. You would end up writing all the integration glue yourself.
- Which Laravel versions does happyr/simplebus-bundle support?
- None officially. Its constraints target symfony/symfony ^2.7|^3.0 and PHP 7-era syntax, while modern Laravel requires Symfony 6/7 components. The 0.1.2 dependency fix does not establish Laravel or PHP 8.2+ compatibility.
- How do I install and configure happyr/simplebus-bundle?
- You require it via Composer and enable the bundle in a Symfony kernel or bundles.php. Configuration happens through the bundle's DI extension and config tree. There is no equivalent registration step in Laravel, so installation alone gives you nothing usable.
- How does happyr/simplebus-bundle register command handlers and event subscribers?
- It tags handler and subscriber services in the Symfony container, with compiler passes doing the auto-tagging. Commands and events remain plain PHP objects. Laravel has no compiler-pass equivalent, so you would need a handler registry using attribute scanning, a classmap, or explicit bindings.
- Does happyr/simplebus-bundle support middleware like transactions and logging?
- Yes, SimpleBus middleware can wrap the command and event buses for Doctrine transaction handling, logging, and domain event dispatch. In Laravel each of these has a direct pipeline equivalent through Bus::pipeThrough() and queue middleware. That overlap means middleware needs rarely justify building a bridge.
- Is happyr/simplebus-bundle maintained and safe for production?
- No. It has roughly 3 stars, zero dependents, and no substantive release since 2017. Version 0.1.2 stepped backward from the 1.x era with a one-line Dependency fix, no visible CI, and no tests. Treat it as abandoned and review any dependency bump as a supply-chain risk.
- What changed in happyr/simplebus-bundle version 0.1.2?
- The release note is a single line: Dependency fix. There is no changelog detail, diff of composer.json constraints, CI signal, or test evidence. Review the commit diff and any new transitive dependencies before letting it near your dependency graph.
- What are the alternatives to happyr/simplebus-bundle for Laravel?
- Illuminate\Bus already provides Dispatcher, ShouldQueue, Bus::pipeThrough(), and the queue plus Horizon stack for command and job execution. If you need CQRS-style command and query separation, use the framework-agnostic simple-bus/simple-bus core directly or a Laravel-native CQRS package. For cross-framework parity with a Symfony service, evaluate Symfony Messenger instead of resurrecting this bundle.
- How would I test happyr/simplebus-bundle in a Laravel app?
- You cannot test it meaningfully in Laravel because there is no integration surface, service provider, or test helper to exercise. Any tests would only cover your own glue code. Before spending time, run composer why-not happyr/simplebus-bundle to confirm whether the dependency constraints resolve at all.
Weaver
How can I help you explore Laravel packages today?