Next steps: Livewire, Inertia and package development

Choosing between Livewire and an Inertia SPA, Livewire component basics, Inertia page props, and packaging a reusable Laravel package.

Choosing the front-end approach

A Livewire component

// app/Livewire/SearchBooks.php
class SearchBooks extends Component
{
    public string $search = '';
    public int $perPage = 10;

    protected function queryString(): array
    {
        return ['search' => ['except' => ''], 'perPage' => ['except' => 10]];
    }

    public function updating(string $field): void
    {
        if ($field === 'search') {
            $this->resetPage();
        }
    }

    public function render(): View
    {
        return view('livewire.search-books', [
            'books' => Book::query()
                ->when($this->search, fn ($q) => $q->where('title', 'like', "%{$this->search}%"))
                ->with('author')
                ->paginate($this->perPage),
        ]);
    }
}

{{-- resources/views/livewire/search-books.blade.php --}}
<div>
    <input type="search" wire:model.live.debounce.300ms="search" placeholder="Search titles">
    @foreach ($books as $book)
        <div wire:key="book-{{ $book->id }}">{{ $book->title }}</div>
    @endforeach
    {{ $books->links() }}
</div>

• wire:key on items inside a loop, or reordering and deleting produce the wrong DOM updates.
• wire:model.live sends a request per change; debounce stops it firing on every keystroke.
• Every Livewire request re-hydrates the component and re-renders on the server, so keep render() queries indexed and paginated.

Inertia page props and packaging

class BookController extends Controller
{
    public function index(Request $request): Response
    {
        return Inertia::render('Books/Index', [
            'books' => BookResource::collection(
                Book::with('author')->withCount('reviews')->paginate(20)
            ),
            'filters' => $request->only('search', 'sort'),
            'can' => ['create' => $request->user()->can('create', Book::class)],
        ]);
    }
}

// partial reloads: only the props a component asks for
Inertia::render('Books/Index', ['books' => fn () => Book::paginate(20)]);
// the client: router.reload({ only: ['books'] })

# scaffold a distributable package
composer require spatie/laravel-package-tools --dev
mkdir -p packages/laravel-metrics/src
cd packages/laravel-metrics && composer init

# in the package composer.json
# "extra": { "laravel": { "providers": ["Acme\\Metrics\\MetricsServiceProvider"] } }
# then: composer require acme/laravel-metrics

• Publish migrations, config and views from the provider so the host application controls them.
• Version with semantic versioning, keep a changelog, and test the package in an isolated Laravel app - the host project can hide missing dependencies.
• Prefer injection or an interface over a facade inside the package, so the host can swap the implementation.

FAQ

Related

Deployment and production hardening Controllers, Blade views and Eloquent models

Last refreshed 2026-09-18.