Client-side island runtime for Blade.
Blade Islands lets you render small React, Vue, or Svelte components inside Laravel Blade views without turning your application into a full single-page app.
This package provides the browser runtime. The Blade directives that render island placeholders live in the companion Laravel package eznix86/blade-islands.
Blade Islands works well when your application is mostly server-rendered but still needs interactive UI in places such as:
Instead of building entire pages in a frontend framework, you can keep Blade as your primary rendering layer and hydrate only the parts of the page that need JavaScript.
Install Blade Islands, your frontend framework, and the matching Vite plugin.
npm install blade-islands react react-dom @vitejs/plugin-react
npm install blade-islands vue @vitejs/plugin-vue
npm install blade-islands svelte @sveltejs/vite-plugin-svelte
Add the runtime to resources/js/app.js, load that entry from your Blade layout, and render an island from Blade.
resources/js/app.js
import islands from 'blade-islands/react'
islands()
Blade layout:
<head>
@viteReactRefresh
@vite(['resources/css/app.css', 'resources/js/app.js'])
</head>
@react('ProfileCard', ['user' => $user])
Resolves to resources/js/islands/ProfileCard.jsx.
resources/js/app.js
import islands from 'blade-islands/vue'
islands()
Blade layout:
<head>
@vite(['resources/css/app.css', 'resources/js/app.js'])
</head>
@vue('ProfileCard', ['user' => $user])
Resolves to resources/js/islands/ProfileCard.vue.
resources/js/app.js
import islands from 'blade-islands/svelte'
islands()
Blade layout:
<head>
@vite(['resources/css/app.css', 'resources/js/app.js'])
</head>
@svelte('ProfileCard', ['user' => $user])
Resolves to resources/js/islands/ProfileCard.svelte.
Blade Islands has two parts:
For example:
@react('Account/UsageChart', ['stats' => $stats])
mounts:
resources/js/islands/Account/UsageChart.jsx
Blade Islands provides framework-specific entry points:
import islands from 'blade-islands/react'
import islands from 'blade-islands/vue'
import islands from 'blade-islands/svelte'
Each entry point mounts only its own island type.
Register the plugin for the framework you use.
import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'
export default defineConfig({
plugins: [react()],
})
If your Laravel layout loads a React entrypoint in development, include:
@viteReactRefresh
import { defineConfig } from 'vite'
import vue from '@vitejs/plugin-vue'
export default defineConfig({
plugins: [vue()],
})
import { defineConfig } from 'vite'
import { svelte } from '@sveltejs/vite-plugin-svelte'
export default defineConfig({
plugins: [svelte()],
})
By default, Blade Islands looks for components in resources/js/islands.
Nested folders work automatically. For example:
@react('Billing/Invoices/Table', [...])
@vue('Billing/Invoices/Table', [...])
@svelte('Billing/Invoices/Table', [...])
These resolve to:
resources/js/islands/Billing/Invoices/Table.jsx
resources/js/islands/Billing/Invoices/Table.vue
resources/js/islands/Billing/Invoices/Table.svelte
If your components live outside the default root, pass both root and components:
import islands from 'blade-islands/vue'
islands({
root: '/resources/js/widgets',
components: import.meta.glob('/resources/js/widgets/**/*.vue'),
})
Then:
@vue('Dashboard', [...])
resolves to resources/js/widgets/Dashboard.vue.
Use preserve: true when the same DOM is processed more than once and you want Blade Islands to keep an existing island mounted instead of mounting it again.
This is useful when the page or a DOM fragment is recalculated and your frontend boot logic runs again.
@react('Dashboard/RevenueChart', ['stats' => $stats], preserve: true)
@vue('Dashboard/RevenueChart', ['stats' => $stats], preserve: true)
@svelte('Dashboard/RevenueChart', ['stats' => $stats], preserve: true)
If you reuse a preserved component in a loop, give each island a unique key on the Blade side so the runtime can distinguish them correctly:
@foreach ($products as $product)
@react('Product/Card', ['product' => $product], preserve: true, key: "product-{$product->id}")
@endforeach
Each entry point exports a default islands() function:
islands({
root: '/resources/js/islands',
components: import.meta.glob('/resources/js/islands/**/*.{jsx,tsx}'),
})
root - component root used to derive names such as Billing/Invoices/Tablecomponents - Vite import.meta.glob(...) map for the current frameworkblade-islands/reactblade-islands/vueblade-islands/svelteThis runtime expects Blade placeholders generated by the Laravel package:
eznix86/blade-islandslaravel-blade-islandsInertia is a better fit when your application wants React, Vue, or Svelte to render full pages with a JavaScript-first page architecture.
Blade Islands is a better fit when your application is already Blade-first and you want to keep server-rendered pages while hydrating only selected components.
MingleJS is often used in Laravel applications that embed React or Vue components, especially in Livewire-heavy codebases.
Blade Islands is more naturally suited to Blade-first applications that want progressive enhancement with minimal architectural change. It does not depend on Livewire, and it may also be used alongside Livewire when that fits your application.
Laravel UI is a legacy scaffolding package for frontend presets and authentication views.
Blade Islands solves a different problem: adding targeted client-side interactivity to server-rendered Blade pages.
npm install
npm test
Contributions are welcome.
npm testMIT