Weave Code
Html Laravel Package
laravie/html
Laravie HTML provides convenient HTML and form builders for Laravel, with a fluent, expressive API for generating forms, inputs, buttons, and other markup in your views. It keeps templates clean, supports model binding and old input, and integrates smoothly with Laravel validation and routing conven...
🔨 HTML and Form Builders for the Laravel Framework
Frequently asked questions about Html
- What is Laravie HTML used for in Laravel?
- Laravie HTML is a view-layer package that provides fluent HTML and Form builders for Laravel Blade templates. It generates forms, inputs, selects, textareas, buttons, labels, links, images, and lists from PHP, reducing repetitive markup. It also supports model binding, automatic CSRF fields, method spoofing, and reusable macros.
- How do I install Laravie HTML in a Laravel application?
- Install it with Composer using composer require laravie/html. Laravel auto-discovery registers the service provider and facades, so no manual wiring is normally needed. You can publish or edit the package config if you need to customize aliases or defaults.
- Which Laravel and PHP versions does Laravie HTML support?
- As of v7.3.0, Laravie HTML explicitly adds Laravel 9 support. Laravel 9 implies PHP 8.0 through 8.2, but you should verify the exact composer.json constraints for your target versions. Support for Laravel 10, 11, and 12 is not confirmed by the provided context.
- Does Laravie HTML support Eloquent model binding?
- Yes, Laravie HTML includes model binding to populate form fields from Eloquent models. It also supports old input repopulation, which is useful after validation failures. Test casts, relations, nested or array inputs, and validation error display on your exact Laravel version because those behaviors are most likely to drift.
- How does Laravie HTML handle CSRF tokens and method spoofing?
- The form builder automatically generates CSRF fields and method spoofing inputs for forms. That keeps PUT, PATCH, and DELETE forms aligned with Laravel routing conventions. Still, confirm test coverage for CSRF and spoofing in your release because form builders are security-sensitive.
- Is Laravie HTML safe from XSS, and are outputs escaped by default?
- Form and HTML builders emit attributes and markup, so escaping behavior is a critical concern. Verify the defaults for HTML::link, HTML::image, and model-bound values, and confirm how raw HTML is explicitly opted into. Any escaping regression or incorrect raw-output behavior should be treated as an XSS risk.
- Can I use Laravie HTML with Laravel 10, 11, or 12?
- The provided context only confirms explicit Laravel 9 support in v7.3.0. It does not state a roadmap for Laravel 10, 11, or 12, so treat those versions as unverified until composer.json constraints and a smoke test pass. If constraints block installation, avoid --ignore-platform-reqs and consider waiting for an upstream patch or forking.
- Does Laravie HTML fit Livewire, Inertia, or API-first Laravel apps?
- Laravie HTML is a server-rendered Blade view-layer package, so it fits traditional Laravel monoliths and CRUD or admin screens best. It is a poor fit for API-first, Inertia, SPA, or heavily component-driven front ends where form state belongs in the client framework or Blade components. Use it where facade-based markup generation reduces repetitive template code.
- How do I create reusable custom builders with Laravie HTML macros?
- Laravie HTML exposes macroable HTML and Form builders, so you can register custom macros for repeated markup patterns. Put the macro registration in a service provider or dedicated bootstrap location, then call it from Blade like a normal builder method. Keep macros small and test their escaping behavior if they output raw HTML.
- What are alternatives to Laravie HTML, and is it still maintained?
- Alternatives include Blade components, legacy LaravelCollective HTML, and client-side form state in Inertia or Livewire apps. Laravie HTML is still viable for server-rendered CRUD screens, but its slow cadence and Laravel 9-only confirmation mean you should compare maintenance and upgrade paths. If you adopt it, keep facade usage contained so a later fork or replacement is less expensive.
Weaver
How can I help you explore Laravel packages today?