Weave Code
Laravel Splade Jetstream Laravel Package
protonemedia/laravel-splade-jetstream
Brings Laravel Jetstream's authentication, teams, API tokens, and profile features to Splade, replacing Jetstream's Vue/Inertia stack with Splade's Blade and Alpine.js approach. Includes matching Splade components and scaffolding for a lighter, JavaScript-driven Laravel app.
Tailwind scaffolding for the Laravel frameworkwith Laravel Splade.
Frequently asked questions about Laravel Splade Jetstream
- What is protonemedia/laravel-splade-jetstream?
- It is a Jetstream stack installer that swaps Jetstream's default Livewire or Inertia frontend for Proton's Splade. Instead of shipping runtime code, it publishes Blade views, routes, controllers, and Vue components into your Laravel application during installation. The result is a SPA-style Laravel app with Jetstream's authentication and profile conventions rendered through Splade. It is scaffolding, not a library you keep in your production dependency graph.
- How do I install laravel-splade-jetstream?
- You install it as a dev dependency with composer require --dev protonemedia/laravel-splade-jetstream, then run the Jetstream install command selecting the Splade stack. The installer publishes the supporting controllers, routes, views, and Vue components into your repository. After publishing, the recommended pattern is to commit the generated code and remove the Composer package entirely. The generated files become yours to own and maintain.
- Which Laravel and PHP versions does this package support?
- The published Composer constraints effectively pin it to the Laravel 9 era with PHP 8.0 through 8.1. It expects Jetstream 2.x and Splade 0.x or 1.x. Applications on Laravel 10 or newer are out of scope unless you fork and manually port the scaffolding. Check the composer.json before assuming compatibility with a modern stack.
- Is laravel-splade-jetstream still maintained?
- No. The repository is archived, with a final release in May 2023, and has no active maintainers or dependents. There will be no CVE response, no Laravel compatibility fixes, and no tracking of newer Splade versions. Any upgrade path runs through your own fork rather than through the package.
- Can I use laravel-splade-jetstream with Laravel 10 or Laravel 11?
- Not without intervention. The package constraints target Laravel 9, PHP 8.0 to 8.1, Jetstream 2.x, and Splade 0.x or 1.x. Since the repo is archived, no one is adding Laravel 10+ support. Running it on a newer app means forking the scaffolding and porting the published assets yourself.
- Is laravel-splade-jetstream a runtime dependency I keep in production?
- No, it is purely a bootstrap-time installer. The install command publishes controllers, routes, views, and Vue components directly into your repository, and that generated code is what runs. The proper pattern is install, publish, vendor, and sever, meaning you commit the generated tree and drop the package from composer.json. Keeping it as a production dependency adds no value.
- Does the Splade stack cover all Jetstream features like teams, API tokens, and two-factor auth?
- Feature parity is the biggest open question and must be verified per project. The generated code inherits Jetstream's Fortify actions, Sanctum, teams, API tokens, profile photos, and password confirmation flows, but the Splade port may omit or stub some of them. Audit each feature you actually need against the published views and routes before committing. Do not assume full Jetstream parity out of the box.
- Is laravel-splade-jetstream safe to use in production?
- Treat the published code as your responsibility to audit. It includes authentication flows, password confirmation, API token issuance, and CSRF-bearing XHR navigation, all of which you inherit and must patch yourself. The MIT license is permissive and the code volume is small enough to review, but an archived 12-star repository has not been scrutinized by a broad community. Splade itself is also single-vendor with a smaller ecosystem than Livewire or Inertia, which raises long-term support and hiring risk.
- How does laravel-splade-jetstream compare to the Livewire or Inertia Jetstream stacks?
- It targets the same problem, a Jetstream-style app with server-rendered Blade and reactive islands, but uses Splade rather than Livewire or Inertia. Splade's middleware returns JSON payloads for SPA-style navigation while Blade renders server-side, which can feel lighter than a full SPA. The tradeoff is a much smaller community, fewer learning resources, and a single-vendor framework. If Splade is not already your team's decision, evaluate Splade itself first rather than entering through this scaffolding package.
- Does the scaffolding work with modern Tailwind 4 and Vite 6 toolchains?
- No, the frontend assumptions are 2023-vintage: Vite with Tailwind 3 and Vue 3. Moving the published assets to Tailwind 4 or Vite 6 requires migration work on the generated files. Because the repo is archived, that migration is entirely on you. Budget time for it if you are starting a new project on a current toolchain.
Weaver
How can I help you explore Laravel packages today?