Laravel Packages

Generate Livewire Skeleton Placeholders Automatically with Wirebones

Published
Generate Livewire Skeleton Placeholders Automatically with Wirebones image

Wirebones by Felipe Martins loads your real page in headless Chromium, traces the rendered layout, and writes a matching skeleton Blade file that Livewire serves while the lazy component boots.

Wirebones-generated skeleton placeholder rendering on the sales
  dashboard demo before the real Livewire component loads
The Wirebones sales dashboard demo mid-load

Because the source of truth is the rendered component instead of a parallel template, redesigns don't silently rot the placeholder — you just rebuild. The author has a live demo with Kanban, sales dashboard, and inbox examples — reload any of them to watch the bones flash before the real markup snaps in.

  • Capture from the real DOM — skeleton markup is generated from the rendered component, not hand-authored
  • Responsive output — capture multiple viewport breakpoints in one build
  • Vite auto-rebuild — file watcher rebuilds only affected skeletons during vite serve
  • Authenticated routes supported — Laravel guard auth, browser cookies, headers, or Playwright storage_state
  • Drop-in to Livewire — works with lazy, defer, and lazy.bundle
  • Laravel Boost skill included — AI agents using Boost pick up the conventions automatically

Marking a component is a single attribute pointing at a route where it's already rendered:

use Livewire\Component;
use MrFelipeMartins\Wirebones\Attributes\Wirebone;
 
#[Wirebone(route: '/dashboard')]
class Revenue extends Component
{
public function render()
{
return view('livewire.revenue');
}
}

Then lazy-mount it as usual and run php artisan wirebones:build:

<livewire:revenue lazy />

The #[Wirebone] attribute also takes a few capture options — viewport widths to snapshot, how long to wait after page load, and selectors to ignore:

#[Wirebone(
route: '/dashboard',
breakpoints: [375, 768, 1280],
wait: 800,
excludeSelectors: ['[data-no-wirebone]'],
)]

Chromium is only used at build time to generate the skeleton Blade files, not at runtime. Once wirebones:build writes the placeholders to disk, Livewire serves them like any other Blade view — your production servers don't need Playwright or Chromium installed.

You can find Wirebones on GitHub and the live demo at wirebones.laravel.cloud.

Paul Redmond photo

Staff writer at Laravel News. Full stack web developer and author.

Sponsored

laravelcloud logo
Laravel Cloud

Easily create and manage your servers and deploy your Laravel applications in seconds.

Visit Laravel Cloud

The latest

View all →
Agent Run Observability in Laravel AI SDK 0.11 image

Agent Run Observability in Laravel AI SDK 0.11

Read article
Debounced Queued Event Listeners in Laravel image

Debounced Queued Event Listeners in Laravel

Read article
Statamic Mailables Viewer Previews Laravel Emails in the Control Panel image

Statamic Mailables Viewer Previews Laravel Emails in the Control Panel

Read article
Laravel Tackle: Run an AI Coding Agent in Your Laravel App image

Laravel Tackle: Run an AI Coding Agent in Your Laravel App

Read article
Queue::forward(): Reroute Laravel Queues in One Place image

Queue::forward(): Reroute Laravel Queues in One Place

Read article
Laravel Read-Through Filesystem: Lazy Storage Migration image

Laravel Read-Through Filesystem: Lazy Storage Migration

Read article