- What Laravel versions does acacha/admin-lte-template-laravel support?
- The package targets roughly Laravel 6 through 8 with PHP 7.3 to 8.0, using Blade, Laravel Mix, and session-based authentication. It was last released in October 2020, so there is no support for Laravel 9, 10, or 11. If you are on a modern Laravel version, plan to copy the Blade layouts and AdminLTE assets into your app instead of installing the package.
- How do I install admin-lte-template-laravel?
- Installation follows the typical scaffolding pattern: require the package with Composer, then publish its views, config, and theme assets using artisan vendor:publish. Because the package pulls in companion packages for menus, breadcrumbs, flash messages, and gravatar, you also need to register those service providers and follow the README setup steps. On current Laravel versions the transitive dependencies usually fail to resolve, so a fresh install is rarely feasible today.
- Is acacha/admin-lte-template-laravel still maintained?
- No. The last release was in October 2020, and there have been no upstream fixes for PHP 8.1+ or Laravel 9+ since then. The 1,795 GitHub stars reflect historical popularity rather than current viability, and Packagist shows essentially no contemporary dependents. Treat it as frozen: if you adopt it, you inherit the fork and all maintenance responsibility.
- Does this package work with Laravel 9, 10, or 11?
- No. The blockers are structural rather than cosmetic: Laravel 9+ replaces Laravel Mix with Vite, upgrades to Symfony 6/7, and changes authentication scaffolding conventions, none of which this package accounts for. It also assumes Bootstrap 3-era asset pipelines and older jQuery plugins. There is no supported upgrade path from this package to Laravel 10 or 11, so a rebuild is the realistic option.
- Does it conflict with Laravel Breeze, Jetstream, Fortify, or laravel/ui?
- Yes. The package ships its own login and registration routes, controllers, and Blade views, which collide with the auth scaffolding from Breeze, Jetstream, Fortify, and laravel/ui. Installing both typically produces duplicate route definitions and view resolution bugs that surface late in development. Pick one auth scaffold per application, or strip the bundled auth out entirely before adding another.
- Which AdminLTE and Bootstrap version does the package ship with?
- The package is built around the AdminLTE theme with Bootstrap 3.0, along with the era-appropriate jQuery and Font Awesome dependencies. That means no Bootstrap 4 or 5 utilities, and it sits below most current accessibility and browser-support baselines. If you need modern AdminLTE 3 or 4, install it from npm and rebuild the layout rather than relying on this package's published assets.
- Should I use this package as a dependency or just copy the Blade views?
- Copy the views. The package is opinionated beyond layout: it reaches into routing, authentication, middleware, and several companion packages, so adopting it is closer to adopting an application skeleton than a UI dependency. Harvesting resources/views layouts, partials, and the AdminLTE distribution assets into your own repository gives you the same look while removing the abandoned dependency graph. This is the approach most teams take for a brownfield Laravel 8 app that already uses it.
- Can I use this package with Vite instead of Laravel Mix?
- Not without work. The package assumes Laravel Mix and precompiled theme assets, while Laravel 9+ defaults to Vite and expects ES module-based asset imports. You would need to rewire the published asset pipeline yourself, at which point you are effectively rebuilding the integration. Extracting the Blade templates and compiling AdminLTE through your own Vite setup is the cleaner path.
- What dependencies does admin-lte-template-laravel pull in?
- It historically bundles companion packages for menus, breadcrumbs, flash messages, and gravatar, plus front-end libraries including jQuery, Bootstrap 3/4, and Font Awesome 4/5. Several of those are end-of-life and carry known XSS exposure, and they often fail to resolve cleanly under modern Composer constraints. Audit the full dependency tree before pinning, and expect to patch or replace the front-end libraries regardless.
- Are there maintained alternatives to this AdminLTE Laravel package?
- Yes. For a modern admin panel you can use AdminLTE 3 or 4 installed via npm, Tabler, Filament, or Backpack, all of which support current Laravel versions and receive ongoing security updates. If you only need the visual shell, an AdminLTE layout plus Laravel Breeze gives you maintained authentication without the legacy dependency graph. Checking whether an approved admin kit already exists in your stack usually removes this decision entirely.