Weave Code
Laravel Forms Laravel Package
fuelviews/laravel-forms
FuelViews Laravel Forms offers a lightweight foundation for defining, rendering, and validating forms in Laravel apps, with reusable form components and Blade-friendly integration to streamline common form-building workflows.
Forms Package
Frequently asked questions about Laravel Forms
- What is fuelviews/laravel-forms used for?
- It is a lightweight Laravel package for defining form fields in a structured, reusable way instead of hand-writing the same markup across views. It focuses on rendering consistent form markup in Blade and keeping submissions tied into Laravel's request and validation flow. It is a foundation for common form-building work, not a full admin-panel generator.
- How do I install fuelviews/laravel-forms?
- Install it with Composer using composer require fuelviews/laravel-forms. Composer will resolve the package against your application's existing Laravel and PHP constraints, so check the reported requirements if the install is refused. After installation, confirm whether the package documentation asks you to publish config or view assets before use.
- Which Laravel versions does fuelviews/laravel-forms support?
- The package is built around Laravel conventions, so it targets the framework versions declared in its composer.json constraints. Rather than guessing, run composer require fuelviews/laravel-forms and let Composer report the compatible release, or check the package page for its Laravel and PHP requirements. If you maintain an older Laravel application, verify support before committing to it in production.
- Does it work with Laravel's built-in validation?
- Yes. The package is designed to integrate with Laravel validation and form requests, so you keep validation rules in the place your application already puts them. Field definitions describe how inputs render, while the validation rules and error messages remain standard Laravel. That means existing FormRequest classes and $errors handling in Blade continue to work as expected.
- How do I render a form in a Blade template?
- Forms are defined in reusable, configurable definitions and then rendered through Blade, which keeps your templates short and consistent. You typically reference the form definition from the view and let the package output the markup for each configured field. Because the output is Blade-friendly, you can style the rendered fields with your existing CSS or Tailwind setup.
- Can I add custom field types or change the default form markup?
- The package is described as extensible, with field types and customization intended to be adjustable rather than fixed. In practice you extend the available field types for inputs your application needs, and adjust the rendering markup so it matches your design system. Review what is published from the package before overriding views, since published files are what you control locally.
- Does it handle old input and validation errors after a failed submission?
- It works alongside Laravel's standard request and validation lifecycle, so old input and the $errors bag behave the way they do in any normal Laravel form. Make sure your form posts through a route that validates with a FormRequest or validator so the framework can redirect back with errors. The package's role is rendering fields consistently, not replacing that framework behaviour.
- Do I need to publish config or view files after installing?
- Many Laravel packages work with sensible defaults and only need publishing when you want to override something. Check the package README for the exact publish commands, since the available tags determine whether config, views, or both can be exported. Publishing is generally only necessary when you need to change default markup or configuration.
- How do I test forms built with fuelviews/laravel-forms?
- Test the behaviour rather than the markup by writing Laravel feature tests that post to your form endpoint and assert validation errors or successful redirects. Because validation stays in standard FormRequests, your existing assertions on session errors and old input still apply. Add a rendering test that hits the page and checks for expected field names when the form definition itself is important to your application.
- Is fuelviews/laravel-forms a good alternative to Livewire or Filament, and is it production-ready?
- It solves a narrower problem: defining and rendering reusable server-rendered forms in Laravel, without the reactive component model of Livewire or the full admin-panel scaffolding of Filament. If you only need consistent form markup and validation wiring, a lightweight package like this avoids pulling in a larger stack. Before adopting it, check the repository's recent commits, tagged releases, and issue activity, since maintenance signals matter more than feature lists for production dependencies.
Weaver
How can I help you explore Laravel packages today?