Laravel Forge + Breeze Default Views#476
Conversation
|
BTW, I could not figure out the failing tests. I updated this to tailwindcss v4 (package.json), modified the vite and tailwind config to support this change and deleted the postcss.config.js as it is no longer needed. When i do the following on my machine, the assets build: laravel new test_app
composer require "laravel/breeze"
this results in a working app and "npm run build" successfully completes. It feels like I am missing something about the github workflows / build. Anyone? |
|
Thanks for your pull request to Laravel! Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include. If applicable, please consider releasing your code as a package so that the community can still take advantage of your contributions! |
|
released as a package: https://packagist.org/packages/rcravens/breeze |
|
I did release a video (https://tekcasts.com/play/pragmatic-laravel-new-fortify-breeze-package ) that walks through the "why" and "how" of this package. |
Problem This Solves
I recently created a Laravel 12 application using the following options:
After some development, I realized that I would like to add authentication. I installed Laravel Fortify to handle all the backend routes / middleware / etc. I then manually pulled in the Laravel Breeze views.
*** NOTE: Pulling in Laravel Breeze (without this change) and then running 'php artisan breeze:install' over-writes a lot of files that have been developed. I tried that path once and then decided to manually pull in what I needed.
Changes
src/Console/InstallCommand.php
src/Console/InstallsForgeDefaultStack.php (new file)
stubs/forge-default (new directory with assets)