- What is robinthijsen/livewire-fields used for?
- It is a small Laravel view-layer component library that provides reusable Blade form field components for Livewire, currently focused on Checkbox and Select inputs. Its purpose is to cut boilerplate when rendering, binding, and validating those fields inside forms. It is an early-stage package with limited adoption, so treat it as a convenience rather than a critical dependency.
- How do I install robinthijsen/livewire-fields with Composer?
- Install it with Composer, for example composer require robinthijsen/livewire-fields, and pin the version you have actually verified in composer.json. Because the package sits in the presentation layer, integration is usually limited to the views or shared layout that render your forms. Confirm the Laravel and PHP constraints declared in the package's composer.json against your locked versions before bumping.
- Which Laravel and PHP versions does livewire-fields support?
- The package's composer.json is the source of truth for supported Laravel and PHP ranges, and patch releases such as 1.0.3 can adjust those constraints. Check them before upgrading, since a patch can silently narrow or widen the supported matrix. If you use Livewire, also confirm that your installed major version falls inside the declared range.
- Is Livewire a hard dependency for the Checkbox and Select components?
- Livewire is part of the package's intended stack, since the components are designed around Livewire form state and validation flows. Because only Checkbox and Select are implemented as of v1.0.3, the practical dependency surface is small. Verify the declared dependency in composer.json rather than assuming it is optional.
- What changed in version 1.0.3 of livewire-fields?
- Version 1.0.3 is described as a fix to the Checkbox and Select components, but the changelog and any linked issues are the only reliable description of what actually changed. A fix at patch level may alter rendered markup, prop defaults, or old-input and validation binding without changing the public API. Capture before-and-after HTML for representative checkbox and select fixtures so the real delta is visible.
- How do I customize or override the Blade views of livewire-fields?
- If you have published the package views with vendor:publish, your copies shadow the package's Blade files, so an upgrade may appear to have no effect at all. Locate any published views under resources/views/vendor and diff them against the upgraded package templates. Decide per file whether to keep your override or adopt the upstream fix.
- Is livewire-fields safe to use in production?
- It is an early-stage package with limited adoption, so it suits projects that can absorb a small amount of churn. Technical risk is moderate-low and concentrated in markup and CSS drift, checkbox and select state semantics, and client-side model synchronization. Pin the version and review rendered output on every upgrade instead of treating it as a zero-review dependency.
- How do I test checkbox and select fields after upgrading livewire-fields?
- Capture rendered HTML for a matrix of fixtures: single and multiple selects, checked and unchecked checkboxes, array-style names such as foo[], old() repopulation, validation errors, disabled, and required states. Bump the package on a branch and diff the output so any markup change becomes your review surface. Then re-run your form feature tests covering validation messages, old-input repopulation, and mass assignment of checkbox arrays.
- What are good alternatives to livewire-fields for Laravel forms?
- Mature options include hand-rolling your own Blade components, using the form components shipped with established UI kits, or relying on Livewire's wire:model bindings with plain markup. A general-purpose component library offers broader coverage and a longer maintenance history at the cost of more configuration. When you only need two field types, custom components are often the lower-risk choice.
- How do I handle old input and validation errors with these checkbox and select components?
- Old-input repopulation and error display are exactly where checkbox and select components tend to break, particularly for array-based checkbox names and the empty placeholder option in selects. After an upgrade, test those flows explicitly rather than trusting the rendered result. If the package's behavior differs from what you need, override the Blade view or set the value explicitly in your Livewire component.