Weave Code
Bulma Laravel Package
laravel-frontend-presets/bulma
A Laravel frontend preset that replaces the default scaffolding with Bulma, providing ready-made auth views, layouts, and styling so you can quickly build responsive Laravel applications using the Bulma CSS framework.
Bulma Frontend Preset For Laravel Framework 6.0 and Up
Frequently asked questions about Bulma
- What is laravel-frontend-presets/bulma used for?
- It is a Laravel frontend preset that replaces the default scaffolding with the Bulma CSS framework. Running php artisan preset bulma writes ready-made Blade layouts, authentication views, app.scss, and bootstrap.js stubs into your application. It is a one-time developer-experience generator, not a runtime library or production dependency.
- Which Laravel versions support the Bulma frontend preset?
- The package targets Laravel 5.5 through 6.0 and depends on the php artisan preset command. That command was deprecated in Laravel 7 in favour of laravel/ui, so the preset workflow does not exist on Laravel 7 and later. It also does not fit Vite-based scaffolding introduced in Laravel 9 and above.
- How do I install the Bulma preset in a Laravel application?
- Install it as a dev dependency with composer require --dev laravel-frontend-presets/bulma, then run php artisan preset bulma to generate the stubs. Finish with npm install and npm run dev to compile assets. Expect friction from the stub build chain, because node-sass may fail on current Node LTS releases even when the Artisan step succeeds.
- What files does the Bulma preset generate or overwrite?
- It ships stubs for resources/sass/app.scss, resources/js/bootstrap.js, resources/views/layouts/app.blade.php, welcome.blade.php, and the full authentication view set. The preset writes over existing resources/views, resources/assets, and auth views, so any prior customisation is lost. Commit or stash your work and use a clean branch before running it.
- Is laravel-frontend-presets/bulma still maintained?
- The last release was May 2020, there are zero dependents, and there is no signal of active maintenance. The Artisan command it hooks into no longer exists in current Laravel versions. Treat it as unmaintained and consider vendoring the generated Blade and SCSS into your repository instead of keeping it as a live dependency.
- Can I use this Bulma preset with Laravel 9, 10, or 11?
- No, those versions use Vite-based scaffolding and do not include the preset command the package depends on. You can still copy the Blade layouts and SCSS stubs manually and adapt them to your project. The one-command Artisan workflow, however, will not run on those releases.
- Does the Bulma preset work with Vite instead of Laravel Mix?
- The shipped stubs assume Laravel Mix, Webpack, and node-sass, not Vite. If you want to keep the Bulma look on a newer Laravel app, vendor the Blade templates and SCSS into your repo and wire them into Vite manually. Import Bulma directly from npm so you control the version.
- Why does npm install fail when using this Bulma preset?
- The stub build configuration relies on node-sass, which does not build on modern Node LTS versions. Replace node-sass with dart-sass or migrate the asset pipeline to Vite. The PHP side of the preset is usually fine; the frontend toolchain assumptions are the main source of failures.
- Can I use this preset together with laravel/ui or Laravel Breeze?
- No, they conflict because they write to the same view paths and auth scaffolding. laravel/ui supersedes the old preset command, and Breeze uses an entirely different stack. Pick one scaffolding approach and start from a clean working tree to avoid overwritten files.
- What are the alternatives to the Bulma Laravel preset?
- Use laravel/ui for Bootstrap, Tailwind, React, or Vue auth scaffolding, or Laravel Breeze and Jetstream for modern Laravel stacks. If Bulma is still your design system, install Bulma from npm and import it in your own Vite or Mix configuration. The preset is best treated as a reference implementation whose stubs you copy and own.
Weaver
How can I help you explore Laravel packages today?