Weave Code
Wizard Bundle Laravel Package
ruwork/wizard-bundle
ruwork/wizard-bundle is a Symfony bundle for building multi-step wizard flows, helping organize forms and sequential user input into structured, manageable steps with navigation support.
[READ-ONLY] Subtree split of the Ruwork Wizard Bundle
Frequently asked questions about Wizard Bundle
- Can I use ruwork/wizard-bundle in a Laravel application?
- No. ruwork/wizard-bundle is a Symfony bundle built around Symfony's kernel, Bundle registration, DI compiler passes, the Symfony event dispatcher, and likely Twig rendering. Laravel's service container, HTTP kernel, middleware pipeline, and Blade are architecturally incompatible, and there is no adapter layer that makes a Symfony bundle boot inside Laravel. Running composer require on a Laravel service will either fail dependency resolution or install dead code that is never executed.
- What is ruwork/wizard-bundle and what does it actually do?
- It is a Symfony bundle that helps organize multi-step wizard flows, grouping sequential user input into structured steps with navigation support. The package is a read-only subtree split of the RuventS/ruwork-wizard-bundle monorepo. The domain problem it addresses, guided linear onboarding and checkout-style flows, is very relevant to Laravel work, but the implementation targets Symfony only. Treat it as prior art for the pattern rather than a dependency.
- Is ruwork/wizard-bundle still maintained?
- No. The repository is archived, with roughly one star and zero dependents, and the original maintainer is inactive. That means no security patches, no PHP 8.2/8.3/8.4 compatibility work, and no bug fixes, so any flaw in the underlying flow logic stays open permanently. There is also no community to ask questions of, no blog posts, and no forks to lean on, which makes the bus factor effectively one.
- Which PHP and Laravel versions does ruwork/wizard-bundle support?
- It supports no Laravel versions at all, because it is a Symfony bundle rather than a Laravel package. Its PHP constraint is also a risk: a Symfony 3/4-era bundle almost certainly pins PHP 5.6 through 7.x, which rules it out on a modern Laravel 10 or 11 runtime. Check composer.json in the repository if you need the exact constraint, but expect it to be incompatible with current PHP releases.
- How do I install ruwork/wizard-bundle with Composer?
- You should not add it to the composer.json of any Laravel service. Even if dependency resolution succeeds, the Laravel kernel never boots Symfony bundles, so nothing registers, no services are wired, and no routes or templates resolve. The only sensible use of the repository is cloning it into a design spike to read the source.
- What should I use instead of ruwork/wizard-bundle in Laravel?
- Use a Laravel-native option: a Livewire multi-step component, a Filament wizard, or a hand-rolled step registry service. Check what is already in your stack before adding anything, since many teams already have Livewire or Filament covering this ground. Building it yourself is routine framework work and keeps you on supported, patched code.
- How do I build a multi-step wizard in Laravel?
- The usual shape is a Wizard service holding a step registry and transition rules, plus a WizardState repository backed by the session cache and a database table for resumability. Validate each step with a dedicated FormRequest, render the UI in Blade or Livewire, and guard step authorization with middleware or a policy. Expect roughly one to three engineering weeks depending on whether persistence, resume, and branching are in scope.
- Does ruwork/wizard-bundle persist wizard state or support resume after abandonment?
- That is not documented anywhere, and the description is literally just the package name, so the behavior has to be extracted by reading the source. Persistence and resume-after-abandon are the expensive part of any wizard implementation and the part most worth copying if it exists. Confirm whether it writes to session or a database table before assuming the feature is there.
- Is ruwork/wizard-bundle a real state machine or just glue over Symfony Forms?
- Unclear from the outside, and the repository has no discoverable specification. It is likely thin glue over Symfony Forms and possibly Symfony Workflow rather than a full state machine, but that has to be verified in the source. If the real value is conditional next-step selection, that branching logic is the one piece worth reading closely and reimplementing deliberately with tests.
- Can I copy the wizard pattern from ruwork/wizard-bundle into my Laravel app?
- Yes. The MIT license permits reading and reimplementing the pattern without legal friction. Reimplementing is the recommended path: the idea transfers cleanly to a Laravel-native Wizard service, step registry, FormRequest validation, and a Blade or Livewire UI. Keep an internal decision audit trail if you borrow source rather than rewriting from the concept.
Weaver
How can I help you explore Laravel packages today?