- How do I install nwidart/laravel-broadway?
- Install it with Composer using composer require nwidart/laravel-broadway, then publish the package configuration and confirm the service provider is registered. The documented setup assumes a Laravel 5.6 or 5.7 application, so verify your framework version first. Run a smoke test that dispatches a command and handles a domain event before adopting it more widely.
- Which Laravel versions does nwidart/laravel-broadway support?
- The 2.0.2 release explicitly adds Laravel 5.6 and 5.7 support, and the integration assessment treats 5.5 through 5.7 as the practical fit. The release notes do not state support for Laravel 5.8 or newer, so the package compatibility ceiling is effectively 5.7.
- Can I use nwidart/laravel-broadway with Laravel 10 or 11?
- The 2.0.2 release does not state support for Laravel 10 or 11, and the package compatibility ceiling is Laravel 5.7. On a newer Laravel version there is no supported integration path, so the realistic options are fork-and-maintain, replace the package, or defer adoption. Pinning the framework backwards is not a viable production strategy.
- How do I configure the event store in Laravel Broadway?
- Publish the package configuration and set the event store connection and related Broadway bindings there. Laravel Broadway wires Broadway core components into Laravel container, so the event store is resolved through configured bindings rather than hard-coded in your domain code. Confirm the exact driver options against the package config and your Broadway version before relying on them in production.
- Does laravel-broadway register a command bus and event bus?
- Yes. Laravel Broadway registers a command bus and an event bus and binds Broadway core components into Laravel service container. That lets you dispatch commands and handle domain events with less manual wiring, while keeping the Laravel service-provider and configuration workflow.
- What is nwidart/laravel-broadway used for?
- It is a Laravel integration for the Broadway event sourcing library, aimed at CQRS and event-sourced applications. It provides a service provider, publishable configuration, an event store integration, and registered command and event buses. Teams use it to handle commands, domain events, projectors, and read models in a familiar Laravel structure.
- Is nwidart/laravel-broadway actively maintained?
- The newest release, 2.0.2, only adds Laravel 5.6 and 5.7 compatibility, and both frameworks are long past end-of-life. That makes the package maintenance-only or effectively abandoned relative to current Laravel releases. Check the repository for recent commits, issue activity, and whether an active fork or funded successor exists before depending on it.
- What PHP version and dependencies does laravel-broadway require?
- Laravel 5.6 and 5.7 era applications generally imply PHP 7.1 to 7.3, but you should confirm the exact Composer constraints in the package. Run a dependency-resolution dry run before committing, because other packages in a modern estate have likely drifted forward and may conflict. Also verify any required PHP extensions for your chosen event store.
- How should I test a Laravel Broadway integration before production?
- Start with a throwaway branch and run a Composer dependency-resolution dry run against your actual application. Install the package, publish the config, and run your existing test suite plus a smoke test for command dispatch and event handling. The release notes provide no evidence of per-Laravel-version CI coverage, so treat the supported matrix as asserted rather than proven until you verify it yourself.
- What alternatives or migration options exist if I am on a newer Laravel version?
- If you are on Laravel 5.8 or newer, there is no supported path in the package as released. You can fork and maintain the integration, replace it with a maintained Broadway-Laravel integration or another event sourcing package that supports your Laravel version, or use Broadway directly with custom service-provider bindings. Make the adopt, fork, or replace decision explicit and name an owning engineer before adding it to the dependency budget.