Weave Code
Laravel Splade Core Laravel Package
protonemedia/laravel-splade-core
Splade Core is the engine behind Laravel Splade, letting you build reactive single-page applications using Blade and Vue 3 without writing Vue components. It provides the low-level rendering, routing, and component internals that power the broader Splade ecosystem.
A package to use Vue 3's Composition API in Laravel Blade.
Frequently asked questions about Laravel Splade Core
- What is protonemedia/laravel-splade-core and do I need to install it directly?
- It is the core runtime and Blade component layer extracted from Laravel Splade, providing the low-level rendering, routing and component internals that let Blade templates hydrate Vue 3 components through the Composition API. In most applications it arrives as a transitive dependency of protonemedia/laravel-splade, so you rarely install or configure it by hand. Install it directly only if you are building on the core layer itself or maintaining your own fork of Splade. For everyone else the real decision is whether to adopt Splade at all.
- Which Laravel, PHP, Vue and Vite versions does laravel-splade-core support?
- The supported envelope is the Laravel 10 era: PHP 8.1 and 8.2, Vue 3.3 or 3.4, and Vite 4 or 5. The final release shipped on 2024-01-31 and the repository was archived shortly afterwards, so nothing newer has been validated by upstream. Laravel 11 and 12, newer PHP minors and later Vite majors should be treated as unsupported until you prove compatibility with your own build and test suite.
- Is laravel-splade-core still maintained?
- No. The project was archived in early 2024 and the last tagged release is dated 2024-01-31, which means no security response, no CVE triage and no compatibility patches. Any future Laravel major you adopt becomes an internal fork-and-patch project. The bus factor is effectively one, documentation and community channels are frozen, and there is no published security feed to monitor.
- How do I install and set up laravel-splade-core?
- Mechanically it is a Composer require, publishing the config and assets, registering the Splade Vite plugin, and rebuilding assets. Because the package is unmaintained, pin an exact version or vendor a fork into an internal namespace via a VCS or path repository instead of relying on caret ranges. Before anything else, confirm the Blade compiler hook still registers cleanly on your exact Laravel minor, since that single check de-risks most of the integration. A one-to-two week spike covering one form with validation and one modal, deployed to staging, is usually enough to confirm feasibility.
- What is the difference between laravel-splade-core and protonemedia/laravel-splade?
- Splade Core is the engine: rendering, routing and component internals. The full laravel-splade package depends on it and adds the higher-level abstractions developers actually use, such as modals, tables, form helpers and an event bus. Consuming core directly gives you the plumbing without those conveniences, which is why it is usually a transitive dependency rather than a deliberate install.
- Can I use laravel-splade-core with Laravel 11 or Laravel 12?
- Treat it as unsupported until proven otherwise. Splade hooks into Blade's compiler and component-rendering internals, which are semi-private surfaces that shift across Laravel majors, so breakage typically appears at build or compile time rather than at runtime. Getting it working on a current Laravel release is a compatibility patch you own, and that patch should be a prerequisite of adoption rather than a follow-up task.
- How does Splade Core compare to Livewire and Inertia?
- Livewire keeps state server-driven with network round trips, while Inertia renders full-page Vue or React apps against an API-like protocol. Splade Core is a hybrid: Blade renders the initial markup server-side and Vue 3 hydrates individual components in place, with no SPA and no API layer. It suits teams that want reactive UI islands inside an existing Laravel monolith. Livewire and Inertia both have active maintenance and current Laravel support, which Splade Core does not.
- Do I need Node, Vite or SSR to use Splade Core?
- You do not need a Node-side renderer or an SSR process, because the initial markup comes from Blade. You do need a Vue 3 and Vite asset build to compile the hydrated components, so a deployment pipeline without a JavaScript build step is a blocker. The frontend build is the only JavaScript toolchain requirement beyond the package itself.
- How do I test components built with Splade Core?
- Use standard Laravel feature and HTTP tests to assert the server-rendered Blade markup, and browser tests such as Dusk or Playwright to cover hydration and interactivity. Upstream documentation is frozen, so plan to write your own regression tests around the Blade compiler hook and every Splade component you consume. Those tests are what will surface breakage loudly when you upgrade Laravel.
- What are the alternatives to Splade Core and how do I avoid lock-in?
- The realistic exit targets are Livewire 3, Inertia with Vue, or plain progressive Vue islands mounted directly in Blade templates. Lock-in here is feature-shaped rather than just dependency-shaped, so the more Splade-specific surface you consume, such as modals, tables, form helpers and the event bus, the more expensive the migration becomes. Keep that surface behind thin internal wrappers or a strict component naming convention so a later swap does not require touching every view, and define in advance which Laravel upgrade would trigger the exit.
Weaver
How can I help you explore Laravel packages today?