Weave Code
Ui Laravel Package
laravel/ui
Laravel UI provides legacy Bootstrap, Vue, and React frontend scaffolding, including authentication views via the artisan ui command. It still works with current Laravel, but new projects should use Laravel Breeze or Jetstream instead.
Laravel UI is a legacy frontend scaffolding package for Laravel that provides a simple starting point for Bootstrap, React, and Vue applications. It generates ready-to-use authentication views and routes via the ui Artisan command, making it quick to bootstrap login and registration screens.
php artisan ui bootstrap|vue|reactfor basic frontend scaffolding--authflag to generate full login/registration views and routes- Supports Bootstrap CSS framework out of the box
- Compatible with Laravel 9.x–13.x (4.x branch)
- Note: for new projects, consider Laravel Breeze or Jetstream
Frequently asked questions about Ui
- What is laravel/ui used for in Laravel?
- laravel/ui is a code-generation package that publishes Bootstrap, Vue, or React frontend scaffolding and optional authentication views into a Laravel application. It provides the php artisan ui command and presets rather than a long-lived runtime library. After scaffolding, the generated controllers, Blade layouts, assets, and routes become application code. It is best treated as a legacy starter tool, not a permanent runtime dependency.
- How do I install laravel/ui and generate frontend scaffolding?
- Install it with Composer using composer require laravel/ui, then run an Artisan preset command such as php artisan ui bootstrap, php artisan ui vue, or php artisan ui react. Add the --auth flag to publish login, registration, password reset, and related authentication views and controllers. After generation, install frontend dependencies and build assets with your normal Node and Vite workflow.
- Which Laravel versions does laravel/ui 4.x support?
- laravel/ui 4.x supports Laravel 9.x through 13.x according to its compatibility table. Only the latest major version receives bug fixes, so older 1.x, 2.x, and 3.x branches map to older Laravel releases. For new Laravel projects, Laravel Breeze is the recommended first-party alternative. Check the version table before adding it to an existing app.
- How do I scaffold login and registration with laravel/ui?
- Run a preset command with the auth flag, for example php artisan ui bootstrap --auth, php artisan ui vue --auth, or php artisan ui react --auth. This publishes authentication controllers such as LoginController and RegisterController, Blade layouts, route stubs, and related views. You then own and maintain those generated files in your application. It does not provide advanced features like teams, two-factor authentication, or API tokens.
- Should I use laravel/ui or Laravel Breeze for a new Laravel project?
- For greenfield projects, Laravel Breeze is generally the better default because it is the current first-party starter kit and uses Tailwind by default. Choose laravel/ui only when you specifically need its Bootstrap, Vue, or React preset or are matching an existing application standard. Jetstream is the stronger option when you need teams, two-factor authentication, API tokens, or profile management. The laravel/ui README itself points new projects toward Breeze or Jetstream.
- Is laravel/ui still maintained and safe for production?
- laravel/ui is in maintenance mode: it continues to work with supported Laravel versions, but only the latest major receives bug fixes. Security-relevant fixes can land in the package and emitted stubs, as shown by the logout authentication fix in v4.5.2. It can be used in production, but teams should plan for the legacy positioning and avoid treating it as an actively evolving starter kit. For new work, evaluate Breeze or Jetstream first.
- Can I create a custom laravel/ui preset with macros?
- Yes, the ui command is macroable, so teams can register internal presets with UiCommand::macro and custom scaffolding conventions. This is useful when an organization wants a repeatable frontend or authentication scaffold beyond bootstrap, vue, and react. The macro approach still emits application-owned files, so you remain responsible for maintaining and updating the generated code. Keep custom presets aligned with your frontend platform and Vite toolchain.
- What Vite, React, and Vue versions does laravel/ui support?
- laravel/ui 4.x tracks modern frontend tooling, with Vite 5 support added in v4.3.0 and React 18 support in v4.1.0. Vue 3 works through @vitejs/plugin-vue, and v4.6.2 documents a conflict fix for that setup. PHP 8.4 support arrived in v4.6.0. Because the package follows upstream frontend releases, verify your Node, Vite, React, and Vue versions before scaffolding.
- Do security fixes in laravel/ui automatically update my generated auth code?
- No. laravel/ui generates and publishes code into your application, so fixes shipped after you scaffold do not automatically reach your forked controllers, views, or routes. You must re-run the relevant ui command, compare stubs, or cherry-pick upstream changes. Assign ownership of the emitted authentication code and define a process for absorbing security fixes.
- Does laravel/ui require Node and a frontend build step in deployment?
- Yes for the frontend presets. laravel/ui assumes a Node and NPM build step, typically with Vite, to compile CSS and JavaScript into your public build assets. If your deployment pipeline ships PHP-only artifacts, you need to build assets earlier in CI or adjust the pipeline. The package has no database, queue, or external service dependency, so runtime risk is mainly the frontend toolchain.
Weaver
How can I help you explore Laravel packages today?