Weave Code
Light Bootstrap Laravel Package
laravel-frontend-presets/light-bootstrap
A Laravel frontend preset that replaces default auth scaffolding with the Light Bootstrap Dashboard theme, adding responsive Blade admin layouts plus login, register, and password reset views. Install via Composer and the preset command for a clean Bootstrap dashboard UI.
Laravel 10.x Front-end preset for argon
Frequently asked questions about Light Bootstrap
- Does this package support Laravel 10?
- Version 1.0.6 claims a Laravel 10.x update, but the claim is unverified: there is no changelog, no test evidence, and no CI proving the path. The frontend-presets artisan command was removed in Laravel 8, so a genuine Laravel 10 install cannot be using the original preset mechanic unless installation was reimplemented. Confirm from the release diff and a small spike before planning on it.
- How do I install laravel-frontend-presets/light-bootstrap?
- Historically you install it as a dev dependency with Composer and run the preset command, which swaps the default auth scaffolding for the Light Bootstrap Dashboard views and assets. On Laravel 8 and later the preset command no longer exists, so the exact install flow for the claimed Laravel 10 support is unknown. Inspect the repository for a publish or install command before running anything in a real application.
- Is this package abandoned or still maintained?
- The repository was last tagged on 2023-03-13, but a later commit associated with v1.0.6 suggests it is not fully abandoned. The project has roughly 35 stars, zero dependents, and no community feedback to corroborate the release. Treat maintenance as sporadic and the bus factor as low.
- What Laravel versions does this frontend preset support?
- It was originally built for Laravel 5.5 through 7.x, and v1.0.6 explicitly claims a Laravel 10.x update. Support for Laravel 8.x and 9.x is undocumented and should be treated as unknown. Check the composer.json constraints and, more importantly, whether the install mechanic actually works on each version.
- Can I use this preset with Vite and Tailwind?
- No. The frontend stack is Bootstrap 4, a jQuery plugin bundle, and Laravel Mix, none of which align with a Vite, Tailwind, or Livewire-first application. The release note does not claim any asset pipeline migration, so expect the same legacy toolchain. A lower-risk option is to harvest the Blade layouts and theme assets into your own Vite pipeline as a design donor.
- What replaced the Laravel preset command in this package?
- The original frontend-presets contract and artisan preset command were removed in Laravel 8. It is unclear whether the maintainer added a custom install or publish command, a service provider, or expects manual file copying. Read the release diff to see which mechanism, if any, was implemented.
- Will the Bootstrap 4 and jQuery assets build on modern Node?
- Probably not without pinning. The package still relies on Laravel Mix and node-sass, which commonly fail on modern Node versions due to OpenSSL and binary compatibility issues. Plan to pin Node, patch the build, or migrate the assets to Vite before using them.
- Is it safe to use in production and what about licensing?
- The MIT license on the package wrapper is clean, but the bundled Creative Tim Light Bootstrap Dashboard theme assets have separate provenance and redistribution terms that need verification. Bootstrap 4 and the jQuery plugin set are end-of-life, which is a supply chain concern. With no tests or dependents, treat production use as unverified until you validate it yourself.
- What are alternatives to this Light Bootstrap dashboard preset?
- For modern Laravel apps, the default options are Breeze or Jetstream with Tailwind, or a maintained admin kit built on Bootstrap 5 or Tailwind. This package is best treated as a design donor rather than a dependency given its low opportunity score. Only choose it directly if you specifically need its Blade admin views and can verify the Laravel 10 path.
- How can I test whether this preset actually works before adopting it?
- Run a spike in a throwaway Laravel 10 application: require the package, check whether a preset or install command exists, run the asset build, and exercise the login, register, and password reset views. Verify the composer.json constraints and the release diff rather than trusting the release note. If the spike passes, add your own CI coverage before adopting it broadly.
Weaver
How can I help you explore Laravel packages today?