Weave Code
Adminlte Laravel Laravel Package
colorlibhq/adminlte-laravel
AdminLTE Laravel integrates the AdminLTE 3 admin dashboard template into Laravel applications. It provides Blade layouts, authentication views, a configurable sidebar menu builder, and helpers to quickly scaffold a responsive, feature-rich admin panel for your Laravel projects.
Official AdminLTE 4 integration for Laravel — Bootstrap 5.3, vanilla JS, Vite-ready.
Frequently asked questions about Adminlte Laravel
- How do I install AdminLTE for Laravel with Composer?
- Require colorlibhq/adminlte-laravel with Composer, then run php artisan adminlte:install to publish config, views, and assets. For asset-only updates after v1.7.0, run php artisan adminlte:install --only=assets --no-interaction-deps. Avoid --force until you have preserved local customizations.
- How do I publish AdminLTE views, config, and assets in Laravel?
- The adminlte:install command publishes Blade views, config/adminlte.php, and frontend assets. Published files are not automatically refreshed by composer update, so re-publish or patch them after upgrades. Use --force only after backing up local edits.
- Which Laravel versions does colorlibhq/adminlte-laravel support?
- Exact supported Laravel and PHP versions are declared in the package's composer.json. Check those constraints before installing, especially on older Laravel releases, and test on your target version because v1.7.0 also changes frontend chart assets.
- Can I use AdminLTE Laravel for authentication and CRUD admin panels?
- Yes, the package provides AdminLTE Blade layouts, authentication views, and dashboard scaffolding that fit Laravel auth and CRUD workflows. You still implement your application's authorization, validation, and CRUD logic. It is a UI layer, not a full admin generator.
- How do I configure the sidebar menu in AdminLTE Laravel?
- Configure menu items in config/adminlte.php using the package's sidebar menu builder. The Blade layout renders the menu, and you can customize labels, icons, routes, and active states. Re-publish or edit the config carefully because composer update will not merge your local changes.
- What changed when AdminLTE Laravel v1.7.0 moved from ApexCharts to Chart.js?
- v1.7.0 replaces ApexCharts with Chart.js 4 and ships vendor/adminlte/js/charts.js, window.AdminLteCharts, and Chart::config(). The x-adminlte-chart component props are mostly unchanged, but ApexCharts-only options and toolbar features are not fully translated. Treat it as a frontend asset migration, not a drop-in library bump.
- Why are my charts empty after composer update to AdminLTE Laravel v1.7.0?
- Published views and resources/js/adminlte.js are not updated by composer update, so stale ApexCharts code or missing Chart.js assets can leave empty chart boxes. Remove ApexCharts, add chart.js@^4.5, run adminlte:install --only=assets, and re-publish or patch customized files. Then rebuild assets and clear caches.
- How do I migrate custom ApexCharts charts to Chart.js in AdminLTE Laravel?
- Inventory component charts and any direct new ApexCharts calls first. Port custom configs through AdminLteCharts.create(el, config) or Chart::config(), translating only options that have Chart.js equivalents. Unsupported ApexCharts options are dropped, so verify series, axes, and interactions visually.
- How should I test and deploy AdminLTE Laravel charts in production?
- Test dashboards in light, dark, auto, and RTL modes, including charts inside tabs, modals, and collapsed cards. Use visual regression or smoke tests and confirm npm/Vite build and cache-busting output. In production, pin the package version, stage the asset migration, and watch for stale published files.
- What are alternatives to AdminLTE Laravel and how is it maintained?
- Alternatives include other Laravel admin starter kits, Blade UI packages, or building directly on AdminLTE assets; compare feature fit, chart support, and release cadence. For maintenance, check the repository releases, composer.json constraints, and open issues before upgrading. v1.7.0 reduces licensing risk by using MIT-licensed Chart.js 4 instead of ApexCharts.
Weaver
How can I help you explore Laravel packages today?