Weave Code
Laravel Splade Breeze Laravel Package
protonemedia/laravel-splade-breeze
A Laravel starter kit that pairs Breeze authentication scaffolding with Splade, letting you build modern single-page apps using Blade and Vue components—no separate API needed. Includes login, registration, password reset, profile management, and a ready-to-extend UI.
Minimal Laravel authentication scaffolding with Laravel Splade.
Frequently asked questions about Laravel Splade Breeze
- What is protonemedia/laravel-splade-breeze?
- It is a Laravel starter kit that pairs Breeze authentication scaffolding with Splade's Blade-first Vue 3 renderer. You install it once at project kickoff and it generates auth controllers, routes, Blade and Splade views, and Vite config directly into your repository. After that the Composer package is inert, so the generated code becomes yours to maintain.
- How do I install laravel-splade-breeze?
- Run composer require protonemedia/laravel-splade-breeze, publish the assets, and run the Vite build, effectively swapping out the default Breeze stack. It is designed for greenfield projects, so start from a fresh Laravel app rather than layering it onto an existing one. A sandbox spike typically takes only a few hours.
- Does laravel-splade-breeze support Laravel 11 and PHP 8.3?
- Version 2.5.2 added explicit PHP 8.3 and Laravel 11 support in a single pull request from the package author. That support is plausible but has no published compatibility test matrix, so verify the full auth flow on the exact 11.x version you plan to pin. Laravel 12 is not addressed yet.
- Can I use laravel-splade-breeze in an existing Laravel app that already uses Breeze?
- It is technically possible but not recommended, because Breeze has already published controllers, views, and routes, so you end up diffing and overwriting rather than installing cleanly. Asset publishing is destructive by default. Reserve it for greenfield projects where nothing conflicts.
- Do I need Inertia or Livewire to use laravel-splade-breeze?
- No. Splade is a Blade-first hybrid renderer that compiles Vue 3 single-file components through a custom driver and hydrates them on the client. It is explicitly not aimed at teams standardized on Inertia, Livewire, or a separate SPA/API auth flow. Adopting it means committing to Splade's rendering model as an architectural choice.
- What authentication features does laravel-splade-breeze include?
- It includes login, registration, password reset, email verification, and password confirmation, plus profile management views. These are Breeze's auth features rendered through Splade components. The UI is minimal and intended for you to extend.
- Do I need a separate API to build an SPA with laravel-splade-breeze?
- No. Splade lets you build single-page-style apps using Blade templates and Vue components without a separate JSON API. Those Vue components are compiled and hydrated on the client, so the auth flows run inside the same Laravel app. This keeps everything in one codebase without maintaining an extra API.
- Is laravel-splade-breeze actively maintained and safe for production?
- Treat it cautiously. It has a single maintainer, a small following of roughly 15 stars and zero dependents, and a sparse release cadence, and the 2.5.2 release was mostly Dependabot CI bumps with no auth security hardening. That is acceptable for internal tools and prototypes but risky for public-facing auth at scale or anything needing a long support horizon. Check the repository's archive status and open-issue triage before committing.
- How do I keep the generated auth code in sync with upstream Laravel Breeze?
- It does not auto-sync. The generated auth code is a one-time copy, so upstream Breeze security fixes only reach you if the author re-syncs the preset or you port them manually. Budget time for periodic diffing against current Breeze releases.
- What are the alternatives to laravel-splade-breeze?
- Consider Laravel Breeze itself with the Blade, Vue, or React stack if you do not need Splade's hybrid model, Laravel Jetstream for a fuller feature set, or Laravel Fortify if you want headless auth. Inertia and Livewire starter kits are better fits if your team is already standardized on those stacks.
Weaver
How can I help you explore Laravel packages today?