Laravellte Laravel Package

Getting Started

• Requirements first: v2.0 jumps to Laravel 8, Livewire 2, and Alpine 2. If your app is still on Laravel 7 you cannot adopt this release without upgrading the framework first. Check composer.json constraints for laravel/framework, livewire/livewire, and alpinejs before composer require.
• Install & publish: pull the new major, then re-publish any published assets/views (php artisan vendor:publish --force), since the Alpine and Livewire asset pipeline changed. Diff the published files against what you had — Turbolinks-specific script tags and event wiring will need to be deleted by hand.
• Look here first: the package's service provider (for view/component registration), resources/views/layouts/ (the base layout is where @livewireStyles / @livewireScripts and Alpine get loaded), and the config file for any component namespace/prefix settings.
• First use case: render a single full-page Livewire component as a route — Route::get('/dashboard', App\Http\Livewire\Dashboard::class); — and confirm Alpine works inside it with a trivial x-data="{ open: false }" toggle. That one page exercises every moving part of this release (routing, Livewire 2 lifecycle, Alpine 2 init, no Turbolinks).

Implementation Patterns

• Full-page components replace controller + view pairs. Anywhere you previously had Route::get(...) → controller → return view(...) where the view was a thin Livewire wrapper, collapse it into a route that points at the component class directly. Keep a layout assigned via ->layout('layouts.app') in the component's render() or the global livewire.layout config.
• Subfolder components use dot notation. A class at app/Http/Livewire/Admin/Users/Index.php is referenced as <livewire:admin.users.index /> and generated with php artisan make:livewire admin.users.index. This is the release's answer to component sprawl — adopt the folder convention early rather than retrofitting later.
• No Turbolinks means no SPA-style navigation. Navigation is full page loads again. Where you relied on Turbolinks for perceived speed, lean on full-page components plus wire:loading / wire:loading.class for perceived responsiveness, and keep the layout's CSS/JS in a single cached bundle.
• Alpine 2 idioms: data must be a plain object literal in x-data, x-init is the hook for side effects, and $dispatch is the cross-component event bus. Bind Livewire state with @entangle('property') — this is the cleanest bridge between the two and avoids manual dispatchBrowserEvent plumbing.
• Alpine inside Livewire lists: wrap third-party JS widgets (selects, datepickers, editors) in wire:ignore and re-init inside x-init or on livewire:load, otherwise Livewire's DOM diffing resets Alpine state on every render.
• Layout discipline: one Blade layout owning @livewireStyles in <head>, @livewireScripts before </body>, and @stack('scripts') after it. Any view that @extends that layout then only needs its component tag.

Gotchas and Tips

• Turbolinks removal is the real breaking change. Silent failures are almost always orphaned listeners: document.addEventListener('turbolinks:load', ...), data-turbolinks attributes, and the Turbolinks <script> tag in your layout. Grep the whole resources/ tree for turbolinks — Alpine initialization previously hung off that event in many setups, and if you don't move it to livewire:load or x-init, Alpine simply never boots.
• Alpine 2 ≠ Alpine 3. Most tutorials online are now Alpine 3. x-data returning a function, Alpine.data() registration, and $dispatch argument shapes differ. Pin your docs to v2 while you're on this release, or you'll chase phantom bugs.
• Livewire 2 asset ordering. Alpine must load before Livewire's script (or be registered via Livewire's bundled Alpine hook) or components init before Alpine is defined. If x-data is inert but Livewire works, it's ordering, not code.
• Full-page components still need a layout with the Livewire directives. The most common "my component renders raw/unstyled" issue is a route pointing at a component whose layout is missing @livewireStyles.
• Subfolder refactors break existing tags. If you reorganize components into subfolders, every <livewire:foo> reference and every Livewire::component() registration must move to dot notation. Grep for livewire: after any move.
• Debugging loop: browser console for Alpine expression errors (they're swallowed silently in v2), Livewire DevTools / the livewire JS object in console for component state, and php artisan view:clear after publishing view changes.
• Extension points worth using: publish and edit the component stubs if your team has a house style, and override the base layout in your app rather than editing vendor files — you will be diffing again at the next major.
• Pair the upgrade with a regression pass on any JS-heavy page. Turbolinks removal and Alpine 2 land together, so "it's broken" rarely has one cause; bisect by disabling Alpine first, then confirming Livewire renders.