Weave Code
Ui Laravel Package
laravel/ui
Legacy Laravel package that adds Bootstrap, Vue, or React frontend scaffolding and simple auth (login/registration) via Artisan (php artisan ui ... --auth). Works with modern Laravel, but Breeze or Jetstream are recommended for new apps.
Laravel UI utilities and presets.
Frequently asked questions about Ui
- What’s the best use case for laravel/ui in a modern Laravel 13 project?
- Laravel UI is best for small-to-medium projects needing quick Bootstrap/Vue/React scaffolding and basic auth (login/registration). It’s lightweight and integrates seamlessly with Laravel’s Vite setup, making it ideal for teams prioritizing speed over deep customization. Avoid it if you need advanced features like team management or API tokens—consider Jetstream instead.
- How do I install laravel/ui and set up Vue + auth in Laravel 13?
- Run `composer require laravel/ui`, then execute `php artisan ui vue --auth`. This installs Vue 3 scaffolding and generates auth views (login, register, etc.) with Vite support. No extra configuration is needed for Laravel 13’s built-in Vite integration. Run `npm install && npm run dev` to compile assets.
- Does laravel/ui work with Laravel 12 or 13, and what’s the latest compatible version?
- Yes, laravel/ui version 4.x supports Laravel 9–13.x. Check the [README](https://github.com/laravel/ui#supported-versions) for exact version mappings. The package is actively maintained (last release: 2026-03-17), but Laravel recommends Breeze/Jetstream for new projects due to their broader feature sets.
- Can I customize the auth templates (login/register) generated by laravel/ui?
- Yes, the auth templates are Blade files (e.g., `resources/views/auth/login.blade.php`) and can be manually edited. For deeper customization, override the default routes or controllers in `routes/web.php` or `app/Http/Controllers/Auth/`. However, complex changes may conflict with future updates—document your overrides carefully.
- Will laravel/ui break my existing Laravel app if I install it mid-project?
- Laravel UI is designed to be non-destructive and won’t overwrite existing files unless you explicitly run `php artisan ui` commands. It adds new views, routes, and controllers under `resources/` and `routes/`, so conflicts are rare. Always back up your project before running scaffolding commands.
- Do I need Node.js/NPM for laravel/ui, and how does it affect CI/CD?
- Yes, laravel/ui requires Node.js/NPM to compile frontend assets (Vite). This adds a dependency layer—ensure your CI/CD pipeline (e.g., GitHub Actions, GitLab CI) includes steps for `npm install` and `npm run build`. Dockerized environments must include Node.js if using laravel/ui’s frontend features.
- What are the security risks of using laravel/ui’s default auth scaffolding?
- The default auth scaffolding is secure for basic use cases (password hashing, CSRF protection, etc.), but lacks advanced features like multi-factor auth or OAuth2. For production, review the generated code (e.g., `app/Http/Controllers/Auth/`) and add custom validation or middleware as needed. Avoid using it for high-risk applications without extensions.
- How does laravel/ui compare to Laravel Breeze or Jetstream in terms of features?
- Laravel UI is minimal—it provides Bootstrap/Vue/React scaffolding + basic auth. Breeze adds more features (e.g., session management, API tokens) with less opinionation, while Jetstream includes teams, profile management, and livewire support. UI is ~50% faster to set up but lacks scalability for complex apps. Evaluate your needs: UI for simplicity, Breeze/Jetstream for robustness.
- Can I use laravel/ui with Tailwind CSS or Alpine.js instead of Bootstrap/Vue/React?
- No, laravel/ui is tightly coupled to Bootstrap, Vue, or React presets. For Tailwind or Alpine, use a custom Vite setup or packages like `laravel/breeze` (which supports Tailwind). UI’s presets are opinionated—if you need flexibility, consider building your own frontend stack or using Jetstream’s modular approach.
- What should I do if laravel/ui stops receiving updates or is deprecated?
- Laravel recommends migrating to Breeze or Jetstream for new projects. Start by auditing your customizations (e.g., Blade templates, auth logic) and document dependencies. Use a tool like `composer why-not laravel/breeze` to assess migration paths. For existing apps, UI remains functional but may lag in security/compatibility—plan a phased upgrade.
Weaver
How can I help you explore Laravel packages today?