Weave Code
Blade components for your Laravel projects
Frequently asked questions about Advanced Controls
- Can I use allyoullneed/advanced-controls in a vanilla Laravel project without Statamic?
- Yes, but with caution. The package is designed for Laravel/Blade/Livewire and explicitly supports hybrid setups. Avoid Statamic-specific helpers (e.g., `entry()`, `asset()`) or components relying on CMS-specific DOM structures. Test thoroughly, as some edge cases (e.g., PR #20’s `toc` selector) may conflict with Laravel’s default templates.
- What Laravel and Livewire versions does this package support?
- The package requires **Livewire 4** and is optimized for Laravel 9+. Check the [GitHub](https://github.com/allyoullneed/advanced-controls) for minor version notes, but no explicit Laravel 10+ compatibility is stated. Always verify against your Livewire setup, as custom configurations (e.g., middleware) could cause conflicts.
- How do I handle asset loading for CDN-dependent components (e.g., charts) in production?
- Components like charts support CDN configuration (see PR #7), but offline environments may fail. For self-hosted assets, manually include the required JS/CSS in your Laravel asset pipeline (e.g., Vite/Mix). Test in production early—CDN-blocked networks or corporate proxies could break functionality.
- Are these components accessible (WCAG/ARIA compliant)?
- Basic accessibility fixes (e.g., ARIA for Select in PR #21) exist, but the package lacks comprehensive a11y testing. For critical projects, audit components manually or pair with Laravel’s built-in accessibility tools. No WCAG compliance guarantees are provided.
- Will forking the package be necessary for deep customization (e.g., theming, slot props)?
- Possible, but not ideal. The package supports basic attributes (e.g., `class`), but deeper theming (CSS variables, slot props) may require forking. Check the [external docs](https://allyoullneed.com) for extensibility patterns, but expect limited built-in flexibility for complex use cases.
- How do I register these components globally in Laravel’s service container?
- Components use standard Blade syntax (`<x-component />`) and don’t require manual registration. However, if you need singleton binding (e.g., for Livewire components), follow Laravel’s [service provider docs](https://laravel.com/docs/container). PR #12 addresses CLI registration, but edge cases (e.g., nested components) may need custom binding.
- Are there performance concerns with large datasets (e.g., Select components with 1000+ options)?
- No official benchmarks exist, but Livewire’s reactivity model should handle moderate datasets efficiently. For large selects, implement client-side filtering (e.g., Alpine.js) or server-side pagination. Test under load—undocumented optimizations (e.g., lazy-loading) may not be present.
- Can I use these components with Laravel’s Vite or Mix asset pipelines?
- Yes, the package has no explicit conflicts with Vite/Mix. CDN-based assets (e.g., charts) may need manual inclusion in your `resources/js/app.js` or `app.css`. Verify compatibility by checking for duplicate IDs or missing asset paths in production builds.
- What happens if the external documentation site (allyoullneed.com) goes down?
- Critical usage examples and API docs are hosted externally, posing a risk. Bookmark the [GitHub README](https://github.com/allyoullneed/advanced-controls) and cache key snippets locally. For production, consider forking or mirroring essential docs to your project’s `/docs` folder.
- Are there alternatives to allyoullneed/advanced-controls for Laravel/Livewire UI components?
- For Livewire-specific components, explore **Livewire UI** (official), **Filament UI**, or **Laravel Nova’s UI tools**. For Blade-focused libraries, check **Tailwind UI** (with Livewire integration) or **Laravel Jetstream’s components**. This package’s niche focus (Statamic origins) may limit alternatives for vanilla Laravel use cases.
Weaver
How can I help you explore Laravel packages today?