Weave Code
Laravel Html Laravel Package
arcanedev/laravel-html
Arcanedev/Laravel HTML provides HTML and form builders for Laravel, letting you generate forms, inputs, links, and other markup with a fluent PHP API. It simplifies Blade templates, reduces repetitive HTML, and supports Laravel conventions.
arcanedev/laravel-html is a fluent HTML and form builder for Laravel, letting you generate markup through expressive, chainable PHP methods instead of hand-writing templates. It ships with dedicated HtmlBuilder and FormBuilder classes, supports custom macros and components, and integrates cleanly with Blade so views stay readable and maintainable.
- Chainable API for elements, attributes, and nested content
- Dedicated form builder with inputs, selects, checkboxes, and buttons
- Bootstrap-ready helpers and reusable component macros
- Facade and container bindings for quick Laravel integration
- Extensible builders for adding your own methods and markup patterns
Frequently asked questions about Laravel Html
- What is arcanedev/laravel-html used for?
- It is a presentation-layer helper package that provides fluent builders for HTML and form markup in Laravel applications. Developers use it to generate forms, inputs, labels, links, and other elements programmatically in Blade views instead of writing repetitive HTML. It fits server-rendered Laravel monoliths with form-heavy CRUD or admin screens.
- Is arcanedev/laravel-html still maintained?
- The last release was on 2020-11-30, and the repository has low activity with no visible maintainer commitment. There is no known recent CI coverage or active issue triage. Treat it as unmaintained and plan internal ownership or migration if you adopt it.
- Which Laravel and PHP versions does arcanedev/laravel-html support?
- The package was last released in 2020, so its Composer constraints likely target older Laravel and PHP versions. Exact support for current Laravel releases and PHP 8.x must be verified with a compatibility spike before adoption. Check composer.json constraints, package discovery, and service-provider registration in your target app.
- How do I install arcanedev/laravel-html?
- Install it with Composer using composer require arcanedev/laravel-html, then verify whether Laravel auto-discovery registers its service provider and aliases. In older Laravel versions you may need to add the provider and aliases to config/app.php manually. Because the package is old, pin the exact version and test registration in a non-production environment first.
- Does arcanedev/laravel-html work with Laravel 10 or Laravel 11?
- There is no evidence in the provided context that it supports Laravel 10 or Laravel 11. The last release was in 2020, so newer framework versions may hit Composer conflicts or runtime incompatibilities. Run a focused spike covering provider discovery, Blade helpers, and form features before assuming compatibility.
- Is arcanedev/laravel-html a good alternative to Laravel Collective HTML?
- It offers a similar Laravel Collective-style API for generating HTML and form markup, but it is not actively maintained. Laravel Collective or native Blade components are safer choices for greenfield work. If you need API compatibility for an existing app, verify behavior and escaping before swapping packages.
- What Laravel form features should I test with arcanedev/laravel-html?
- Test model binding, CSRF tokens, PUT/PATCH method spoofing, validation error display, old input repopulation, and file uploads. Also check HTML escaping and XSS behavior, since stale form helpers can introduce regressions. A focused proof-of-concept should cover these flows before you approve adoption.
- Does arcanedev/laravel-html have security or XSS concerns?
- The provided context does not list specific advisories, but unmaintained HTML and form helpers can develop escaping or XSS issues over time. You should audit how the package escapes attributes and user input, especially in labels, links, and form values. Monitor Composer audits and consider wrapping or forking the package if you need fixes.
- Can I use arcanedev/laravel-html in an API or Inertia/Livewire application?
- No, it is intended for server-rendered Blade applications, not API-first services or SPA/Inertia front ends. Livewire-heavy UIs and design-system component libraries should use native Blade components or maintained UI packages instead. It adds convenience only where repetitive form markup is rendered server-side.
- How should I migrate away from arcanedev/laravel-html?
- Pin the exact version in composer.lock, isolate usage behind an internal form or HTML helper abstraction, and migrate screens incrementally to native Blade components or a maintained alternative. Document an exit plan and assign internal ownership for upgrades and removal. This limits upgrade risk and lets you remove the dependency when the abstraction is no longer needed.
Weaver
How can I help you explore Laravel packages today?