- Is Laravel UI still recommended for new Laravel projects in 2024?
- No, Laravel UI is officially deprecated for new projects. The Laravel team recommends using **Laravel Breeze** for simpler auth scaffolding or **Jetstream** for more features like teams, API support, and two-factor auth. UI remains functional but lacks modern tooling like Inertia.js or Livewire.
- How do I install Laravel UI and generate auth scaffolding for Bootstrap?
- Run `composer require laravel/ui`, then generate auth scaffolding with `php artisan ui bootstrap --auth`. This creates Blade templates for login, registration, and password reset pages using Bootstrap 5. Ensure your `package.json` and `vite.config.js` are compatible with Laravel’s Vite setup.
- Can I use Laravel UI with Vue 3 or React 19 in Laravel 11+?
- No, Laravel UI currently supports **Vue 2** and **React 18** (as of v4.x). For Vue 3 or React 19, you’ll need to manually migrate components or use alternatives like Breeze/Jetstream, which support modern frontend versions. Check the [README](https://github.com/laravel/ui) for version compatibility.
- Will Laravel UI work with Laravel 14 when it releases?
- Laravel UI is actively maintained for Laravel 13 as of 2026, but there’s no guarantee of support for Laravel 14. The package is **not recommended for greenfield projects**—migrate to Breeze or Jetstream to avoid future compatibility risks. Audit your auth logic (e.g., `AuthenticatesUsers` trait) for conflicts.
- How do I customize the auth templates generated by Laravel UI?
- Generated templates (e.g., `resources/views/auth/login.blade.php`) are standard Blade files. Edit them directly, but note that UI’s Vue/React components (e.g., `ExampleComponent.vue`) are tied to its scaffolding structure. For deep customization, replace the entire `resources/js` or `resources/css` folders and update `vite.config.js`.
- Does Laravel UI support Tailwind CSS instead of Bootstrap?
- No, Laravel UI is **Bootstrap-specific**. To use Tailwind, install it separately (`npm install -D tailwindcss`) and replace Bootstrap’s CSS/JS in `resources/js/app.js` and `vite.config.js`. Remove leftover Bootstrap scaffolding files (e.g., `node_modules/bootstrap`) to avoid conflicts. Consider Breeze/Jetstream for Tailwind-ready presets.
- Can I integrate Laravel UI with a custom auth system (e.g., OAuth, SAML)?
- Laravel UI’s auth scaffolding relies on Laravel’s default `AuthenticatesUsers` trait and session handling, making it difficult to integrate with third-party auth like OAuth or SAML. For custom auth, use Laravel Fortify or build a solution from scratch. UI is best for standard email/password flows.
- How do I set up Laravel UI with Vite in a CI/CD pipeline?
- Run `npm install` and `npm run build` in your CI pipeline (e.g., GitHub Actions) to compile assets. Ensure your `vite.config.js` includes Laravel’s Vite plugin. Test the build locally first (`php artisan vite:build`) to catch Node.js/Vite compatibility issues. UI’s Vite integration is lightweight but may slow down pipelines for large projects.
- What are the alternatives to Laravel UI for scaffolding auth in Laravel?
- **Laravel Breeze** is the official replacement for UI, offering simpler auth scaffolding with Bootstrap, Tailwind, or Pinia (Vue) support. **Jetstream** provides advanced features like teams, API resources, and two-factor auth. For headless APIs, use **Laravel Fortify** with Inertia.js or a custom frontend. Evaluate based on your needs: Breeze for simplicity, Jetstream for features.
- How do I migrate from Laravel UI to Laravel Breeze or Jetstream?
- Start by removing the `laravel/ui` package (`composer remove laravel/ui`). Install Breeze/Jetstream via their installers, then manually migrate auth views (e.g., `resources/views/auth`) and logic (e.g., controllers, middleware). Replace UI’s Vue/React components with Breeze’s or Jetstream’s. Test auth flows thoroughly, especially password resets and email verification.