Weave Code
Laravel Multi Step Progressbar Laravel Package
genealabs/laravel-multi-step-progressbar
A Laravel package by GeneaLabs for adding configurable multi-step progress bars to your app, perfect for multi-step forms and wizards. It offers a simple API and Blade component to track the current step, with customizable labels and styling, and requires minimal setup.
At a glance
Frequently asked questions about Laravel Multi Step Progressbar
- How do I install genealabs/laravel-multi-step-progressbar in a Laravel app?
- Install it with composer require genealabs/laravel-multi-step-progressbar. Setup is minimal: optionally publish the package views and config, then include the Blade component in your wizard layout. There are no migrations or meaningful service provider steps to configure.
- Which Laravel and PHP versions does laravel-multi-step-progressbar support?
- The 10.0.0 release from May 2023 only certifies Laravel 10 compatibility. Other Laravel majors are unverified, so treat it as Laravel 10 only until you confirm composer.json constraints and test it. Check whether illuminate/* is pinned to ^10.0 and whether PHP 8.2 or 8.3 is admitted.
- Is genealabs/laravel-multi-step-progressbar still maintained?
- It shows weak adoption and sustainability signals: around 63 stars, zero dependents, a single maintainer, and no release in more than two years. Treat it as unmaintained until there is visible activity on the issue tracker. For production, fork-and-own is the realistic default.
- How do I define and label steps in the progress bar?
- Steps can be defined through configuration, a prop array, or the published view, depending on the package version and setup. Publish the views and config immediately so step composition and styling live in your codebase. That choice determines how much of your wizard composition is trapped inside a third-party abstraction.
- Does this package include accessible ARIA markup for step indicators?
- Assume the emitted markup is incomplete for accessibility and audit it against the ARIA progress indicator pattern. A correct stepper needs ordered step semantics, role=progressbar where appropriate, aria-current on the active step, and live-region announcements when the step changes. Remediating accessibility after ship is harder than writing it correctly upfront.
- Can I customize the progress bar colors and styling to match my design system?
- The package exposes configurable colors and sizes, but its common framework defaults mean you will likely need override work. Publishing views is where the real styling cost sits, not in Composer. Validate the rendered output against your design tokens at desktop and mobile breakpoints.
- Does laravel-multi-step-progressbar work with Livewire, Inertia, or Vue?
- This is a Blade-first presentational component, so it fits poorly with Livewire-heavy, Inertia, React, Vue, or headless SPA stacks. In those stacks the stepper belongs in your internal component library, not in a third-party Blade package. Use it only for a Laravel 10 Blade-first stack with a real multi-step UX.
- Does the package ship JavaScript for animated step transitions?
- First confirm what the component actually encapsulates: static markup only, or JavaScript for transitions you would inherit and have to own. The package description emphasizes a simple Blade component, but the rendered surface should be verified before adoption. Any inherited JS becomes your maintenance responsibility.
- What are the best alternatives to a Laravel multi-step progress bar package?
- The strongest alternative is a 50 to 150 line internal Blade partial plus the design and accessibility review that partial needs anyway. If your design system already defines a stepper, building or reusing it avoids override work and upgrade coupling. A package is only worth it if its output matches what UX would design.
- Should I fork or vendor laravel-multi-step-progressbar for production?
- With one maintainer and zero dependents, fork-and-own is the realistic default if you adopt it. Treat adoption as prototype-grade: install behind a feature flag, publish views and config immediately, and QA against design tokens and an accessibility checklist. Pinning without a fork still leaves a decorative component as a potential upgrade blocker.
Weaver
How can I help you explore Laravel packages today?