Weave Code
Uikit3 Laravel Package
laravel-frontend-presets/uikit3
A Laravel frontend preset that replaces the default Bootstrap scaffolding with UIkit 3, providing prebuilt authentication views, layouts, and assets so new apps start with a clean UIkit foundation. Install via Composer, run the preset command, and begin building.
Laravel 5.5.X Front-end preset for UIKit 3.
Frequently asked questions about Uikit3
- What Laravel versions does laravel-frontend-presets/uikit3 support?
- It targets Laravel 5.5.x through 6.x, where the php artisan preset command still exists. Laravel 7 removed the preset command in favor of laravel/ui, so the package's main entry point no longer works on 7 or later. On newer versions you can still copy the stub files out of the repository manually.
- How do I install laravel-frontend-presets/uikit3?
- Run composer require --dev laravel-frontend-presets/uikit3, then execute php artisan preset uikit3. Laravel's package auto-discovery registers the service provider, so there is no manual wiring in config/app.php. After the command finishes you should run npm install and npm run dev to build the assets.
- Does this preset work with Laravel 8, 9, 10, or 11?
- Not as intended. The preset Artisan command was removed in Laravel 7, and from Laravel 9 onward the default asset pipeline is Vite rather than Laravel Mix. The Blade layout and auth views remain portable, but the webpack.mix.js build config is obsolete for modern targets. The pragmatic approach is to harvest the stubs from the repo instead of depending on the package.
- What files does the uikit3 preset overwrite in my application?
- It replaces package.json, webpack.mix.js, the resources/assets js and sass directories, the base Blade layout, and the authentication views for login, register, and password reset. The command writes in place, so it can silently clobber customizations on an existing app. Always commit a clean baseline or work on a fresh tree before running it.
- Is laravel-frontend-presets/uikit3 still maintained and safe to use in production?
- The upstream is effectively frozen, with a small star count and no dependents, so every bug fix and UIKit upgrade becomes your responsibility. There is no runtime code, middleware, or container binding, so it adds no request-path security exposure. The one caveat is that the generated authentication Blade templates are scaffolding you must audit and own before shipping.
- Does laravel-frontend-presets/uikit3 use Laravel Mix or Vite?
- It uses Laravel Mix. The preset publishes a webpack.mix.js file and the Blade layout relies on the mix() helper to resolve compiled assets. It predates Vite entirely, so on Laravel 9 and newer you would need to rewrite the build configuration yourself.
- Can I run this preset on an existing Laravel app that already has custom auth views?
- You can, but it is destructive by design and overwrites the authentication views and asset config in place. On anything other than a pristine tree this can erase customizations without warning. Either commit a baseline first so you can diff the result, or copy the stub files individually and merge them by hand.
- How do I upgrade UIKit or fix npm install errors after running the preset?
- Once the preset runs, you own the generated files entirely and there is no upgrade channel. Bump the uikit version in package.json and update the Mix plugins yourself. Stale pins in the stubs commonly fail against current Node toolchains, so expect to adjust dependency versions on a fresh machine.
- What are good alternatives to laravel-frontend-presets/uikit3?
- For Laravel 7 and later, use laravel/ui to scaffold auth and then install uikit via npm manually. Laravel Breeze and Jetstream ship Tailwind-based scaffolding if the team is framework-agnostic. Bootstrap and Tailwind both have materially deeper ecosystems, so pick UIKit 3 only if it is a real product requirement.
- How do I set up UIkit 3 manually in Laravel without this preset?
- Install uikit with npm, import it in resources/js/app.js, and add your own SCSS entry point. Then replace the default Blade layout and auth views with your own markup. Alternatively, copy the stub files straight from the GitHub repository and adapt them, which avoids carrying an unmaintained dev dependency in composer.json.
Weaver
How can I help you explore Laravel packages today?