Weave Code
Livewire Forms Laravel Package
nodus-it/livewire-forms
A Laravel Livewire package for creating dynamic, reusable forms with validation and model binding. It simplifies form state management and Blade rendering, helping you build complex forms faster with less boilerplate in Livewire applications.
A awesome package for easy dynamic forms with Laravel Livewire and Bootstrap v4
Frequently asked questions about Livewire Forms
- What is nodus-it/livewire-forms and what does it do?
- It is a presentation-layer package for Laravel Livewire that lets you declare dynamic, reusable forms as PHP classes instead of inline Blade markup. It bundles field metadata, validation wiring, model binding, and Blade rendering so complex forms need less boilerplate. It owns no persistence, queues, transport, or schema, so its blast radius is limited to how forms are declared and rendered.
- How do I install nodus-it/livewire-forms in a Laravel application?
- Installation follows the usual Composer flow: require the package, publish its config and Blade views, then have your Livewire component inherit from the package's form base class. The friction is not installation itself but that the package is opinionated about form declaration, so it reaches into component structure and view composition. A contained spike on one non-critical form is a cheap way to confirm the fit.
- Which Laravel, PHP, and Livewire versions are supported?
- The supported version matrix is not documented in the provided material and is explicitly listed as an open question for this package. The description targets Laravel applications using Livewire and Bootstrap 4 views at version 0.11.2. Check the composer.json constraints in the repository before committing, and confirm whether Livewire 3 is first-class or bridged.
- Does nodus-it/livewire-forms work with Livewire 3?
- Livewire 3 support is unconfirmed in the reviewed material; whether Livewire 3 is first-class or bridged is flagged as a key question to resolve. Because the package's value is inseparable from Livewire's component lifecycle, a Livewire major version is a forcing function on this dependency. Validate against your exact Livewire version with a small proof-of-concept form before adopting broadly.
- How does validation work with this package?
- The package provides validation wiring for form fields, but the material reviewed does not confirm whether it delegates to Laravel's validator and FormRequest or implements its own rules. That distinction matters, because duplicating rules in both the form object and a FormRequest invites drift. Confirm the validation behavior and error message handling in a spike before relying on it.
- Can I customize the form views and styling?
- Blade views are published as part of setup, and the package description targets Bootstrap v4 rendering. Whether rendering uses overridable published Blade files or a custom render pipeline determines how cheap design-system alignment will be. If your application uses Tailwind or a custom design system, verify view overridability first, since that is where most of the styling effort goes.
- Does it support dynamic, nested, repeater, and file upload fields?
- The overview advertises dynamic forms, but nested fields, repeaters, and file uploads are exactly where form abstractions typically fail and are flagged as unresolved questions. These capabilities are not documented in the reviewed material. Test your most complex real form, including uploads, before committing to the package.
- How does model binding work for edit forms?
- The package supports model binding, letting form fields map to an Eloquent model so edit forms avoid manual hydration boilerplate. Combined with the validation wiring, this is where the package saves the most code on typical CRUD screens. Also check mass-assignment behavior and any authorization hooks before pointing it at sensitive models.
- Is nodus-it/livewire-forms stable enough for production at version 0.x?
- It is pre-1.0 at v0.11.2, so minor bumps such as 0.12.0 may legally include breaking changes, and the v0.11.2 release artifact is a changelog link with no notes. Budget for validating upgrades by diffing source or running your own test suite rather than reading release notes. Maintenance is single-vendor with no commercial backing, which caps how deep the dependency should go.
- How hard is it to remove or migrate away from this package later?
- Removal is genuinely low-friction because the package has no database footprint or persisted state: drop the Composer dependency and published views and you are back to plain Livewire forms. A strangler approach works well, applying it to greenfield forms only while leaving existing FormRequest and Blade forms untouched. Avoid mixed-mode forms that combine the package's form objects with manually managed state, since those complicate rollback.
Weaver
How can I help you explore Laravel packages today?