Compatibility
| Requirement | Supported |
|---|---|
| PHP | 8.0, 8.1, 8.2, 8.3, 8.4 |
| Laravel | 8.x and 9.x (end-of-life, see below), 10.x, 11.x, 12.x, 13.x |
| Database | Anything Eloquent supports (MySQL, MariaDB, PostgreSQL, SQLite, SQL Server) |
| Browser | Current Chrome, Edge, Firefox, Safari (the Tailwind template uses backdrop-filter and :has()) |
| Node.js | Not required at runtime; only to rebuild the Tailwind template |
| Laravel | PHP | Status in 1.3.0 |
|---|---|---|
| 13 | 8.3, 8.4 | Supported, in CI |
| 12 | 8.2, 8.3, 8.4 | Supported, in CI |
| 11 | 8.2, 8.3, 8.4 | Supported, in CI |
| 10 | 8.2, 8.3 | Supported, in CI |
| 9 | 8.0, 8.1, 8.2 | Supported, in CI; verified with the full suite and browser checks on PHP 8.1 |
| 8 | 8.0, 8.1 | Supported, in CI; verified with the full suite and browser checks on PHP 8.0 |
| 4, 5, 6, 7 | 5.3 – 8.0 | Not supported |
Laravel 8 and 9 are end-of-life. Both have published security advisories, and Composer 2.8 or newer refuses to install them unless you set composer config audit.block-insecure false in the application. Use them only for existing applications that cannot be upgraded yet, and plan the upgrade.
Why Laravel 4 to 7 cannot be supported. They run on PHP 5.3 to 8.0 and lack the framework APIs the package is built on: Laravel 4 has no middleware, no namespaced service-provider resource loading and no package discovery; Laravel 5 to 7 predate the PHP 8 syntax used throughout the package (union and nullable types, typed properties) and the Symfony 5.4+ components it depends on. Supporting them would mean rewriting the package for those PHP versions, with no security updates on either side. Upgrade the application first (the Laravel upgrade guides or Laravel Shift), then install Super Admin.