- How do I install zareismail/nova-wizard in a Laravel Nova app?
- Install it with Composer using composer require zareismail/nova-wizard, then register the tool in your NovaServiceProvider::tools() method if the README calls for it and publish any assets. After that you create a wizard class that declares ordered steps as arrays of native Nova fields and wire it into the resource's fields() method. Check the package README and composer.json first, because exact registration steps depend on the Nova version it targets.
- Which Laravel and Nova versions does nova-wizard support?
- The package has not seen a release since August 2023, so its composer.json constraints are the authoritative answer and you should read them before installing. Given that timeline it is most likely built for Nova 4 and its Vue 3 asset pipeline, and Nova 5 compatibility is unproven. Run a version check against your pinned Nova, Laravel, and PHP versions before you invest any build time.
- How do you define wizard steps with nova-wizard?
- Steps are declared through a fluent API in a base wizard class, with each step containing an ordered array of standard Nova fields. The wizard effectively slices the flat array returned by a resource's fields() method into named, sequential steps rendered inside Nova's existing form. Because the steps hold native Nova fields rather than custom components, your existing field configuration carries over.
- Does nova-wizard work with both resource create and update forms?
- Yes, the package is designed to reshape fields() during both create and update, so the same wizard definition covers new records and edits. It does not introduce a parallel resource or a separate controller path, which means Nova's store() and update() behavior is preserved. Always confirm this on a representative resource with a short proof of concept before rolling it out broadly.
- Do my existing Nova fields and validation rules still work inside a wizard?
- The package reuses native Nova fields, so field types, validation rules, relationships, and policies should continue to behave as before. It is a presentation and navigation layer, not a replacement form engine. File fields and conditional fields are the most likely areas to need extra testing, especially regarding when uploads are actually submitted.
- Is wizard state preserved when users navigate forward and back between steps?
- State is preserved as users move forward and back through the steps, so partially completed input is not lost during navigation. What happens on a full page refresh is a separate question and is not clearly documented, so test whether state is client-only or backed by a session. If you need resumable drafts, plan to add your own persistence columns.
- Does nova-wizard require a Node or Vite build step?
- The package advertises itself as lightweight with no extra frontend build required, which implies prebuilt assets. Verify that a compiled dist/ directory is actually committed in the repository or distributed package before assuming this. If it is missing, you would need a Node toolchain matching the package's Vue version to compile assets yourself.
- Is per-step validation enforced on the server side?
- Nova's standard validation runs on final submission through the resource's normal rules, so data integrity is generally covered at that point. Whether each step is validated server-side before the user advances is less certain and may be client-side gating only. This matters for both data integrity and authorization, so confirm it in a spike rather than assuming.
- Is zareismail/nova-wizard actively maintained, and what are the alternatives?
- Signals suggest a small, single-maintainer project with roughly 14 stars, no dependents, and no visible CI or test suite, so treat maintenance as a real risk. Alternatives include building a custom multi-step Vue component, splitting the form across Nova panels or tab fields, or simply restructuring the resource into smaller ones. If the guided flow becomes business-critical, budget for a fork you control.
- How should I evaluate nova-wizard before using it in production?
- Start with a version feasibility check against your pinned Nova, Laravel, and PHP versions, then install it on a branch and rebuild one existing create form as a two-step wizard. In that spike, test refresh behavior, file uploads, validation scoping, and authorization to see whether the flow holds up. Given the package's age and thin documentation, approve it only as a timeboxed spike for internal admin screens with a documented fork-or-replace plan.