Weave Code
Aire Laravel Package
glhd/aire
Aire is a modern, fluent form builder for Laravel. Define fields and layouts in PHP or Blade, bind models, surface validation errors, and render clean, accessible HTML forms through a simple, component-based API.
Modern form builder for Laravel
Frequently asked questions about Aire
- What is glhd/aire and what does it do?
- Aire is a modern, fluent form builder for Laravel. It lets you define fields and layouts in PHP or Blade, bind Eloquent models, surface validation errors, and render clean, accessible HTML forms through a component-based API. It is a presentation-layer package and does not replace Laravel's validation or persistence.
- How do I install Aire in a Laravel application?
- Install it with Composer using composer require glhd/aire, then optionally publish its config and Blade views if you need to customize defaults. Adoption is incremental, so you can introduce Aire on one form without converting existing forms. Check the README for any publish commands and version constraints.
- Which Laravel versions does Aire 2.16.0 support?
- The 2.16.0 release documents added support for Laravel 13 with no listed breaking changes or deprecations. The exact supported range and any PHP constraints should be confirmed in the package's composer.json. If you are on Laravel 11 or 12, treat 2.16.0 as a low-risk minor upgrade but still verify resolution in CI.
- Does Aire work with Livewire, Inertia, or SPA front-ends?
- Aire is designed for server-driven Laravel and Blade applications where forms are rendered and validated server-side. It is a weaker fit for API-first services, Inertia/SPA front-ends, or stacks that already have a form abstraction. If you use Livewire or Alpine for dynamic behavior, verify that Aire's client-side story composes with those tools rather than duplicating them.
- Can Aire bind models and display validation errors?
- Yes. Aire is built around Laravel's native facilities for model binding and validation, so you can bind an Eloquent model to a form and surface validation errors in the rendered HTML. The package's purpose is to make those common form concerns fluent and consistent. Test rendering and error display in your own feature tests.
- How do I define fields and layouts in Aire?
- You can define fields and layouts in PHP or Blade using Aire's fluent, component-based API. This lets you keep form definitions close to your application code while rendering accessible HTML. Start with a small form to learn the vocabulary, then expand usage where it adds clarity.
- Is upgrading to Aire 2.16.0 safe?
- 2.16.0 is a semver-minor release whose only documented change is added Laravel 13 support, with no listed breaking changes or deprecations. For teams already on Aire, it should be a near-zero-risk upgrade that widens the framework constraint. Still verify transitive dependency resolution and run your form-level tests, especially if you are moving to Laravel 13.
- How should I test forms built with Aire?
- Use Laravel feature tests to assert the rendered HTML, model binding, and validation error behavior for each form. Aire does not remove the need for application-level test coverage; it changes how the form is defined and rendered. Include at least one test per form that submits invalid data and checks the surfaced errors.
- What are alternatives to Aire for Laravel forms?
- Common alternatives include hand-written Blade components with FormRequest validation, Livewire or Alpine for dynamic forms, and admin-panel tools such as Filament. Aire is a good fit when you want a server-rendered, accessible form abstraction in PHP or Blade. For Inertia or SPA stacks, use the front-end form approach native to that stack.
- What maintenance or production risks should I consider with Aire?
- Aire is a smaller open-source project without a commercial support contract, so maintainer concentration and security-response posture matter. Published config and Blade views can drift because Composer does not update them, so track those customizations. Have an internal owner and an exit plan, and validate edge-case behavior on new Laravel versions in CI.
Weaver
How can I help you explore Laravel packages today?