- How do I install okipa/laravel-form-components?
- Run composer require okipa/laravel-form-components in your Laravel project. No configuration file needs to be published to get started, and the anonymous Blade components are available immediately under the form:: namespace. You can then drop components such as x:form::input or x:form::select straight into your Blade views.
- Which Laravel, PHP and Livewire versions are supported?
- Package version ^1.3 targets Laravel ^12.0 or ^13.0, PHP ^8.3 and Livewire ^2.0. Older releases cover Laravel 8 through 10 on PHP 8.0 to 8.2, also with Livewire 2. Check the compatibility table before upgrading Laravel, PHP or Livewire, since the package trails framework releases.
- Is okipa/laravel-form-components compatible with Livewire 3?
- The documented compatibility matrix only declares Livewire ^2.0, and version 1.3 is not listed as tested against Livewire 3. If your application is Livewire 3 only, run a spike on a representative form before committing to the package. Otherwise treat Livewire 2 as the supported baseline.
- Does this package work with Tailwind CSS?
- Bootstrap 5 and Bootstrap 4 are the supported UI frameworks today. TailwindCSS 3 is listed in the README as an upcoming feature and has not shipped. If your design system is Tailwind-based, the package's core value does not apply, so wait for the Tailwind release or choose a Tailwind-native alternative.
- How do I bind a model and display validation errors with these components?
- Pass :bind="$user" to x:form::form and the child inputs, selects and textareas inherit that model's values. Validation state is read from Laravel's $errors bag, so components render error styling on the fields whose rules failed. This keeps your Blade templates short without custom form logic.
- How does x:form::form handle CSRF tokens and PUT, PATCH or DELETE method spoofing?
- Set the method attribute on x:form::form, for example method="PUT", along with an :action, and the component emits the CSRF token plus the hidden _method field automatically. You do not need manual @csrf or @method directives in your views. The wrapper also renders the surrounding form tag and its attributes.
- How can I customize the generated form markup?
- The package ships anonymous Blade components, so you can override the views to match your own Bootstrap theme or accessibility requirements instead of forking the repository. Overriding is the intended route when you need ARIA associations, extra wrapper classes or different label placement. Keep your overrides in version control so package upgrades remain predictable.
- How do I migrate from okipa/laravel-bootstrap-components to this package?
- Follow the published upgrade guide: the old facade helpers such as inputEmail(), inputPassword(), submit() and buttonCancel() all map onto a smaller set of new components. Work file by file with visual regression checks rather than one mass rewrite. The guide flags undocumented changes, so budget time for edge cases you discover along the way.
- Is this package actively maintained and safe to use in production?
- It is MIT licensed with full source, but it has a single maintainer, a small star count and no commercial backing, and releases have gapped by years. The risk is well bounded: it is pure presentation layer with no database, queue, auth or deserialization surface, so blast radius is low. Forkability is your mitigation, so keep an internal owner who can patch Blade views if upstream goes dormant.
- When should I avoid this package, and what are the alternatives?
- Skip it for Tailwind-based design systems, Inertia or Vue/React front ends, and Livewire 3-only applications. It suits internal tools, admin panels, CRUD-heavy back offices and MVPs on Laravel 9 to 13 with Bootstrap. If you need Tailwind output or a faster release cadence, prefer a Tailwind-native component library or hand-rolled Blade components.