Weave Code
Bootstrap 4 Laravel Package
laravel-frontend-presets/bootstrap-4
A Laravel frontend preset that swaps the default scaffolding for a clean Bootstrap 4 setup, publishing ready-to-use layouts, views, and authentication templates. Run the preset command and start building responsive Laravel apps with Bootstrap 4 styling already wired in.
Laravel 5.5.x Front-end preset for Bootstrap 4
Frequently asked questions about Bootstrap 4
- How do I install laravel-frontend-presets/bootstrap-4?
- Require the package as a dev dependency with composer require laravel-frontend-presets/bootstrap-4, then run php artisan preset bootstrap-4 to overwrite the default front-end scaffolding. Finish with npm install followed by npm run dev to compile the new Bootstrap 4 assets. Because it is a scaffolding generator and not a runtime library, the Composer dependency does not need to stay in your project afterward.
- Which Laravel versions does this preset support?
- It targets Laravel 5.5.x, the release that introduced the php artisan preset command, and works with caveats on 5.6.x. Laravel 5.7 relocated the resources/assets directory and the preset command was later deprecated and removed from the framework. Any application on 5.7 or later cannot run the preset as designed, and laravel/ui is the officially maintained successor path.
- Does this preset work with Laravel 6, 7, 8, 9 or newer?
- No. The preset depends on the php artisan preset command, which no longer exists in the framework, and on the resources/assets directory layout that was moved in Laravel 5.7. On modern Laravel versions you should use laravel/ui with php artisan ui bootstrap, or scaffold the Bootstrap entry points by hand. There is no partial-compatibility middle ground here; it either matches the framework version or it does not.
- What is the difference between this preset and laravel/ui?
- This package is an era-specific preset built for Laravel 5.5, while laravel/ui is the officially maintained replacement that provides php artisan ui bootstrap for Laravel 6 and later. laravel/ui offers the same outcome, swapping Tailwind-style scaffolding for Bootstrap entry points, layouts and auth views, but with ongoing maintenance and community support. If you are on a version that supports laravel/ui, that is the obvious choice over this preset.
- Which Bootstrap version does this preset generate, and is it still supported?
- It generates Bootstrap 4 scaffolding, including Sass entry points, JavaScript imports, layouts and navbar markup. Bootstrap 4 reached end of life at 4.6.2 and Bootstrap 5 shipped in May 2021, so the generated front end carries unpatched-issue risk and a shrinking documentation base. If your desired end state is Bootstrap 5, this package solves the wrong problem and you should scaffold against Bootstrap 5 directly.
- Why does npm install or npm run dev fail with node-sass errors?
- The preset pins an era-appropriate toolchain: Laravel Mix 1.x or 2.x on webpack 3 and a Sass compilation path that expects node-sass. node-sass is deprecated and does not build on modern Node LTS releases, so reproducible installs require pinning a Node version that is itself out of security support. You can either pin that Node version in your build environment or migrate the Sass pipeline to Dart Sass, which usually means updating Mix as well.
- Does this package affect my application at runtime or in production?
- No. It registers no service provider in the request lifecycle and ships no models, migrations, routes or configuration, so it has zero production runtime footprint. Its blast radius is confined to build tooling and committed asset sources such as resources/assets/sass/app.scss, resources/assets/js/bootstrap.js and package.json scripts. It is effectively a code generator rather than a library you depend on at runtime.
- How do I remove the preset once it has been applied?
- Treat it as a one-shot generator: install it, run php artisan preset bootstrap-4 once, then remove it from composer.json and commit the resulting files. The generated Sass, JavaScript, layouts and auth views are plain source files in your repository and do not reference the package at runtime. Removing the Composer dependency afterward leaves no abandoned package for your team to maintain.
- Is laravel-frontend-presets/bootstrap-4 still maintained?
- There is no meaningful maintenance signal: the repository shows no stars and no dependents, and the source appears untouched since roughly the Laravel 5.5 launch window. With no active maintainer there is nobody to triage a supply-chain or toolchain issue, and nothing will be updated for newer Laravel or Node releases. Plan to treat it as a frozen artifact of a specific era rather than a dependency you can rely on long term.
- What are the alternatives to this preset for Bootstrap scaffolding in Laravel?
- The preferred options, roughly in order, are to skip the package and commit the Bootstrap Sass and JavaScript entry points plus package.json changes by hand, or to use laravel/ui with php artisan ui bootstrap on Laravel 6 and later. For newer applications, Breeze and Jetstream are the default scaffolding choices, though they ship with Tailwind rather than Bootstrap. Adopting this preset as a one-shot generator and then removing it is a reasonable fallback if you must hold a Laravel 5.5 codebase.
Weaver
How can I help you explore Laravel packages today?