- How do I install smajti1/laravel-wizard in a Laravel app?
- Install it with Composer using composer require smajti1/laravel-wizard and let Laravel package discovery register the service provider. Plan to publish configuration and Blade views if your setup needs overrides. On older Laravel versions, confirm whether manual provider registration is required.
- Does laravel-wizard support Laravel 11 and Laravel 12?
- The package's last release is from December 2023, so Laravel 11 and 12 support is not confirmed by the provided context. Check its Composer version constraints and run a short compatibility spike on your target Laravel and PHP versions before adopting it. Do not downgrade Laravel solely to use this package.
- Is smajti1/laravel-wizard suitable for Inertia, Livewire, or API-first apps?
- It is best understood as a server-rendered Blade and session-oriented wizard component, so it is a weaker fit for API-first, SPA, Inertia, or Livewire-heavy applications. You could use it as a backend wizard-state helper behind your own abstraction, but frontend state management may be simpler. Confirm the rendering model before committing.
- How does laravel-wizard handle validation between steps?
- The package is built around dedicated step classes, so validation is intended to live with each step and its navigation rules. Keep domain validation and authorization in application-owned classes or services rather than embedding business rules in package step classes. Verify the exact validation hooks and failure behavior in a sandbox flow.
- Can wizard state be persisted and resumed across sessions or devices?
- Wizard state appears to be session-oriented, and the context does not confirm built-in resume across devices. If resume is required, treat the package as a rendering and navigation layer and persist step data through your own model or service. Test session expiry and cross-device behavior explicitly.
- Can I customize or override the Blade views and routes in laravel-wizard?
- The package provides Blade views and configurable step definitions, and its publishing setup is intended to let applications override presentation details. Confirm whether routes, views, and step classes can be overridden cleanly without forking, and watch for route namespace collisions. Wrapping package usage in an application-owned adapter reduces lock-in.
- Is smajti1/laravel-wizard actively maintained and safe for production?
- Risk is moderate: the package has low visible adoption, a single-maintainer profile, and a last release from December 2023. MIT licensing helps because you can vendor or fork it, but that makes it an internally owned component. Use it for lower-risk internal flows, not core revenue or compliance workflows without a fork plan and named owner.
- How do I test multi-step wizard flows built with laravel-wizard?
- Write feature tests around step transitions, validation failures, session expiry, and successful completion, ideally through an application-owned adapter. Keep domain logic outside package classes so tests focus on your flow rather than package internals. Add a compatibility test in CI for your Laravel and PHP versions.
- What are alternatives to smajti1/laravel-wizard for multi-step forms in Laravel?
- Alternatives include a custom Laravel controller and Blade flow, Livewire wizard components, Inertia or SPA-managed steps, or another maintained Laravel wizard package. Choose based on whether your app is Blade and session-based or API and SPA-oriented, and weigh maintenance activity and Laravel version support. For simple linear flows, a small in-house implementation is often lower risk.
- Does laravel-wizard work with Redis or database sessions and horizontal scaling?
- The context does not confirm behavior with Redis, database sessions, or horizontal scaling, so test your session driver in a staging environment. Session-backed wizards usually need a shared session store and consistent routing across nodes. If you run multiple app servers, verify sticky sessions or shared storage before rollout.