- What are the requirements for shipbytes/laravel-ui-kit?
- It requires PHP 8.2+, Laravel 12, Livewire 3.6+, Fortify, Volt, and Tailwind CSS v4. Laravel 13 is allowed in the Composer constraints, but the CI leg for it is explicitly experimental. Confirm your PHP and Laravel versions match before installing.
- How do I install laravel-ui-kit in a Laravel app?
- Require the package with Composer, then run php artisan ui-kit:install. The installer publishes files, patches config, runs migrations, storage:link, npm install, and vendor:publish for dependencies. A preflight collision check and publish map help you spot conflicts before running it, and a short manual checklist covers the User trait, layout tags, Tailwind preset, Vite imports, and .env.
- What files does ui-kit:install publish into my application?
- It publishes Blade views, Livewire and Volt components, routes, migrations, and configuration files into your app. It also patches config/fortify.php, config/admin.php, and routes/admin.php between marker comments. After installation the published code is yours to maintain, so treat it as a fork rather than a normal runtime dependency.
- Which optional modules are included in laravel-ui-kit?
- The seven optional modules are admin-middleware, support-tickets, changelog, contacts, profile, impersonation, and activity-log. Some pull extra Composer packages such as spatie/laravel-permission, mews/purifier, lab404/laravel-impersonate, and spatie/laravel-activitylog. Modules that ship models also ship factories for use in your tests.
- Does laravel-ui-kit support two-factor authentication?
- Yes. The core install includes a two-factor challenge page in the Fortify and Volt login flow, covering TOTP and recovery codes. The enable and confirm UI ships with the optional profile module, which also provides full self-service 2FA management.
- Can I use laravel-ui-kit alongside Laravel Breeze or Jetstream?
- No. Breeze and Jetstream coexistence is explicitly unsupported, and the installer hard-aborts when it detects Jetstream. Existing customized Fortify views and actions may be silently skipped or overwritten depending on the force option, so brownfield apps typically need Breeze removed first.
- Is laravel-ui-kit available on Packagist with tagged releases?
- The README includes an appendix for installing via a VCS or path repository until a version is tagged and submitted to Packagist. That means you should verify a stable semver tag exists before committing. If only dev-main is available, many organizations will require vendoring or forking instead of pinning a branch in production.
- What does the ui-kit:doctor command check?
- The ui-kit:doctor command is a health check that verifies the install is fully wired. It is intended to catch missing pieces from a partial scaffold, such as unpublished views, missing layout tags, or configuration that was not patched. Run it after installation and after any manual edits.
- How do I upgrade laravel-ui-kit after customizing the published files?
- There is no documented upgrade contract for published files you have modified, so you effectively own a fork from the first install. Re-running the installer over hand-edited files is a merge problem the package does not solve. Plan to vendor or fork the scaffold and track upstream changes manually.
- Is laravel-ui-kit production-ready and well tested?
- CI runs a fresh-app install, build, route:cache, and HTTP smoke test on every push, and modules with models ship factories. However, the project has zero stars, zero dependents, a bus factor of one, and no evident security policy or release governance. Treat it as unproven and pilot it in a non-critical app before production adoption.