Weave Code
Advanced Controls Laravel Package
allyoullneed/advanced-controls
A collection of advanced Blade components for Laravel that helps you build polished, good-looking websites with minimal effort. Install via Composer and drop the components into your templates like any other Blade component.
UI components for Statamic, powered by Livewire 4
Frequently asked questions about Advanced Controls
- How do I install allyoullneed/advanced-controls in a Laravel project?
- Install it with Composer by running composer require allyoullneed/advanced-controls from your Laravel project root. Then use the package's Blade components in your templates like any other Blade component. The README says the full component list and documentation are on the project website.
- Does allyoullneed/advanced-controls work with Livewire?
- Yes, the package is described as purpose-built for Laravel Blade and Livewire reactivity, and recent commits add wire:model support for tabs and selects. The technical evaluation notes an assumption of Livewire 4, so verify compatibility with your Livewire version and configuration. Test dynamic binding in your own app before relying on it.
- Is allyoullneed/advanced-controls only for Statamic or can I use it in vanilla Laravel?
- The README presents it as a Laravel Blade component library, and the evaluation says Laravel compatibility is explicitly claimed even though the package has Statamic origins. The risk is undocumented assumptions from Statamic helpers or CMS syntax, so test the components you need in a vanilla Laravel app. Do not assume every component is CMS-independent without verification.
- What Laravel versions does allyoullneed/advanced-controls support?
- The README excerpt does not list Laravel version constraints, and the technical evaluation notes an assumption of Livewire 4 plus early-stage maturity. Check the repository composer.json and release notes before installing in a production Laravel app. Pin a version that you have tested with your Laravel and Livewire stack.
- Does allyoullneed/advanced-controls require Tailwind, Alpine, or other frontend dependencies?
- The evaluation describes it as lightweight and MIT-licensed with no external dependencies beyond Livewire and Blade, though chart components can use configurable CDNs. The README excerpt does not document a hard Tailwind or Alpine requirement. Check component-specific documentation because asset handling and styling assumptions may vary by component.
- How do I customize the look of advanced-controls components?
- You can pass standard Blade attributes such as class, and the components are intended to fit Laravel templates without major refactors. The evaluation warns that deeper theming via CSS variables or slot props may require forking. Test Tailwind and Vite setups before standardizing on the package across a project.
- Can I use the chart components without a CDN or in an offline environment?
- Charts support configurable CDNs, but the evaluation warns that offline or corporate-proxy setups may need manual asset handling. Self-host the chart assets and test loading through your Laravel asset pipeline. Do not assume CDN defaults will work in restricted networks.
- Is allyoullneed/advanced-controls production-ready?
- It is early-stage with active 1.1.x fixes, zero stars and dependents in the evaluation, and no documented deprecation or backward-compatibility policy. That does not make it unusable, but it raises the risk of breaking changes and undocumented edge cases. Pin versions and test critical flows before production use.
- Where is the documentation for allyoullneed/advanced-controls?
- The README points to the project website at allyoullneed.com for the component list and documentation. The technical evaluation flags this external documentation as an availability and freshness risk. Keep a local record of the component APIs you rely on.
- Does allyoullneed/advanced-controls support accessibility and ARIA attributes?
- Recent fixes include ARIA attribute work such as the Select PR, but the evaluation found no evidence of comprehensive accessibility testing or WCAG compliance. Treat accessibility as something you must verify for your own use cases. Audit interactive components like tabs and selects against your required standards.
Weaver
How can I help you explore Laravel packages today?