Weave Code
Wizard Laravel Package
ruwork/wizard
Ruwork Wizard is a lightweight PHP package for building step-by-step forms and guided workflows. Define ordered steps, manage navigation and validation, and turn complex processes into clear, sequential wizards with a simple, reusable API. Ideal for onboarding, checkout, and other multi-stage user j...
[READ-ONLY] Subtree split of the Ruwork Wizard
Frequently asked questions about Wizard
- What is ruwork/wizard used for?
- ruwork/wizard is a lightweight PHP library for modeling step-by-step forms and guided workflows. It lets you define ordered steps and manage navigation and validation so multi-stage journeys such as onboarding or checkout have a clear flow. It is a thin domain abstraction, not a full UI or Laravel wizard component.
- Is ruwork/wizard a Laravel package or a plain PHP library?
- Treat it as a plain PHP library that you wrap in Laravel application code. The available assessment says it is unlikely to ship a service provider, config file, or facade, and it does not own routing, views, or ORM concerns. You would register bindings and adapters yourself.
- How do I install ruwork/wizard with Composer?
- Install it with Composer using the package name ruwork/wizard, then autoload it through Composer in your Laravel app. Because the repository is an archived read-only subtree split, confirm the Packagist metadata and composer.json constraints before adding it. For production use, the safer path may be vendoring the source into an application namespace.
- Does ruwork/wizard support Laravel 10, 11, or 12?
- The provided information does not list supported Laravel versions, and the package is not described as Laravel-integrated. Its composer.json may pin older PHP or Symfony constraints that conflict with current Laravel releases. Test it in a throwaway container against your exact PHP and Laravel matrix before committing.
- Is ruwork/wizard safe to use in production?
- Runtime risk is described as modest because the domain is simple, but lifecycle risk is high. The repository is archived, has one star, zero dependents, and no maintainer surface for bug fixes, security patches, or version drift. Use it only with a plan to own the code, or choose a maintained alternative.
- Does ruwork/wizard provide Livewire or Blade wizard components?
- No, the available assessment explicitly says it is not a drop-in Livewire or Blade wizard component. It models steps and flow state but leaves controllers, validation, persistence, and UI to your application. Expect to build the presentation layer yourself.
- How does ruwork/wizard integrate with Laravel validation and FormRequests?
- The overview mentions managing validation, but the provided material does not document a Laravel Validator or FormRequest integration. Wizard libraries can assume specific validation semantics, so inspect the source and write characterization tests around step validation. You may need an adapter that maps each step to your own FormRequest rules.
- Where does ruwork/wizard store wizard state?
- The available information does not specify whether flow state lives in the session, the request, or user-supplied persistence. The assessment warns that wizard libraries often assume session-backed state, which may not match your Laravel architecture. Confirm this in the source before designing persistence or resume flows.
- Does ruwork/wizard support conditional steps and prevent step skipping?
- The overview describes ordered steps and transitions but does not document branching or server-side ordering enforcement. Do not assume conditional steps or skip protection until you verify the source and tests. If you adopt it, enforce allowed transitions server-side in your own wrapper.
- Should I require ruwork/wizard from Packagist or vendor it into my app?
- For a greenfield wizard, the assessment recommends wrapping any flow behind an internal contract such as WizardFlow so the implementation can be swapped. Because the package is abandoned, vendoring the relevant classes into an application namespace converts it into owned code and avoids supply-chain and upgrade conflicts. If you need maintained Laravel integration, evaluate building a small state machine in-house or a maintained alternative.
Weaver
How can I help you explore Laravel packages today?