- How do I install Tablar in a Laravel 12 project?
- Run `composer require takielias/tablar` and select the Laravel 12 preset. Follow the branch-specific docs (e.g., `12.x/README.md`) for Vite setup, Blade overrides, and auth scaffolding. The package includes a `tablar:install` Artisan command to automate the process.
- Does Tablar work with Livewire or Inertia.js?
- Yes, Tablar is framework-agnostic but includes basic Livewire/Inertia.js compatibility. For Livewire, register components in `app/Providers/AppServiceProvider`. For Inertia, extend `resources/views/app.blade.php` with Inertia’s `<head>` and layout wrappers. Check the docs for framework-specific integration steps.
- Can I customize the Tabler theme (colors, icons, dark mode)?
- Tablar uses CSS variables (e.g., `--tabler-primary`) for theming. Override these in `resources/css/app.css` or via Vite’s `postcss.config.js`. For icons, replace `@tabler/core` with a custom icon set by extending the Vite config. Dark mode toggles are pre-built but can be reconfigured via Blade directives.
- What Laravel versions does Tablar officially support?
- Tablar supports Laravel 10, 11, and 12 with dedicated branches (e.g., `10.x`, `11.x`). Each branch includes version-specific fixes (e.g., Vite 4+ for Laravel 11/12). Laravel 13 support is implied but untested; check the GitHub issues for updates. Pin your Laravel version in `composer.json` to avoid conflicts.
- Will Tablar conflict with existing Laravel UI packages (e.g., laravel/ui, Jetstream)?
- Tablar replaces `laravel/ui` with a Breeze-inspired auth scaffold. If using Jetstream/Fortify, override auth views in `resources/views/vendor/tablar/auth` or extend Tablar’s auth logic. Database/auth logic remains untouched—only Blade templates are replaced. Run `php artisan vendor:publish --tag=tablar-views` to customize.
- How does dynamic menu generation work in Tablar?
- Tablar uses Laravel’s route caching and Blade directives (`@tablar.active`) to highlight active menu items. Menus are defined in `config/tablar.php` as an array of routes/URLs. For nested menus, use the `submenu` key. Dynamic menus auto-update when routes change, reducing manual menu management.
- Is Tablar optimized for production? Does it bloat my build?
- Tablar uses Vite with ESBuild for tree-shaking, minimizing bundle size. Exclude unused Tabler plugins (e.g., `@tabler/core/plugins`) in `vite.config.js`. Audit chunks with `npm run build -- --analyze` to identify bloat. Production builds are ~50% smaller than default Tabler setups due to Laravel’s asset optimization.
- Can I use Tablar with a monolithic Laravel app (not a fresh install)?
- Yes, but expect minor conflicts. Tablar installs into `resources/vendor/tablar` and overrides `app.blade.php`. Merge custom views into `resources/views/vendor/tablar` or adjust view paths in `config/view.php`. Test with `php artisan tablar:install --force` to preview changes before committing.
- What if I need to replace Tabler’s core components (e.g., custom tables, modals)?
- Tablar’s components (tables, modals) are Blade-based and can be overridden by publishing assets (`php artisan vendor:publish --tag=tablar-views`). For deep customization, extend the Vite config to replace `@tabler/core` with a custom CSS/JS library. Document overrides in `config/tablar.php` to avoid merge conflicts.
- Are there alternatives to Tablar for Laravel admin dashboards?
- Alternatives include **CoreUI Laravel** (Bootstrap-based), **AdminLTE Laravel** (AdminLTE integration), and **Filament** (headless admin panel). Tablar stands out for its Tabler UI (modern, dark-mode-ready) and Laravel-native structure. If you need a headless solution, Filament offers more flexibility; for a pre-built UI, Tablar is faster to implement.