WireKit v2.8.1
Patch release. A Livewire 4 layout-setup documentation correction plus a matching installer-hint fix — fully backward-compatible.
Fixed
wirekit:installnow names the correct layout path in its no-layout hint. When no app layout exists and Livewire'slivewire:layoutcommand is unavailable, the installer's fallback instruction pointed atresources/. On a fresh Livewire 4 app the layout actually belongs atviews/ components/ layouts/ app. blade. php resources/(Livewire 4's defaultviews/ layouts/ app. blade. php layouts::appnamespace), so the hint now names that path.
Documentation
- The Getting Started layout walkthrough now matches what the installer actually creates. It recommended
resources/and pinned the example page-component toviews/ components/ layouts/ app. blade. php #[Layout('components.— but on a fresh Livewire 4 app (no Starter Kit),layouts. app')] wirekit:install, via Livewire's ownlivewire:layout, createsresources/(Livewire 4's defaultviews/ layouts/ app. blade. php layouts::app). Following the old steps left#[Layout]pointing at a file that was never created. The page now frames the two real cases (fresh app vs. Starter Kit), drops the#[Layout]attribute from the example (Livewire's default already wraps the component in the created layout), and clarifies thatmake:livewirescaffolds empty stubs you fill in and that the route is yours to add.