Weave Code
Livewire Starter Kit Laravel Package
artisanpack-ui/livewire-starter-kit
ArtisanPack UI Livewire Starter Kit is a Laravel scaffolding package for building Livewire apps with ArtisanPack UI components. It offers ready-to-use layouts, authentication screens, and UI foundations to help you launch admin panels and internal tools faster.
The perfect starting point for your next Livewire project. It handles all the boilerplate for authentication and user management, giving you a clean, solid, and secure foundation to build upon immediately.
Frequently asked questions about Livewire Starter Kit
- How do I install artisanpack-ui/livewire-starter-kit for a new Livewire project?
- Install it the same way you would any Laravel starter kit, either through Composer or the laravel new installer flow, and the scaffolding will lay down the Livewire layouts, authentication screens, and ArtisanPack UI component wiring for you. In non-interactive environments the installer falls back to a path where the setup command must be run manually after the initial install. Plan for that explicit manual step in your provisioning scripts, Dockerfiles, and CI pipelines so unattended builds do not end up half-scaffolded.
- Does this starter kit support Laravel 12?
- No. Version 2.0.0 drops Laravel 12 support entirely and targets Laravel 13 only, removing the previous ^12.0|^13.0 constraint. If you are still on Laravel 12, stay on the 1.0.3 compatibility range or complete a dedicated Laravel 13 upgrade branch before adopting v2. Do not try to combine the framework upgrade and the starter kit upgrade in the same change set.
- What PHP version does the ArtisanPack UI Livewire Starter Kit require?
- The v2 line requires PHP 8.3 or higher, and the supported range spans PHP 8.3, 8.4, and 8.5. That means you should remove PHP 8.2 jobs from CI and pin your runtime images to a supported 8.3+ version before scaffolding. MySQL and MariaDB SSL CA handling is now consistent across that whole PHP range, so database TLS configuration should behave the same on 8.3 through 8.5.
- What is included in the starter kit out of the box?
- It ships ready-to-use Livewire layouts, authentication and user management screens, and UI foundations built on ArtisanPack UI components, so you can go straight to building admin panels and internal tools instead of writing boilerplate. The scaffolding also sets opinionated defaults around Vite, Pest, and Tinker, plus an optional-packages command for pulling in companion packages. Think of it as an opinionated application skeleton rather than a drop-in runtime library you add to an existing app.
- What is the recommended migration path from v1 to v2 of the starter kit?
- Treat it as a coordinated upgrade on its own branch, not something you mix with feature work. Bump PHP to 8.3+, upgrade Laravel to 13, align laravel/tinker, laravel/boost, Pest, and PHPUnit, then move the ArtisanPack UI companion packages to their Laravel 13-ready majors and rebuild the frontend on Vite 7 with laravel-vite-plugin 2. If you cannot reach Laravel 13 immediately, remain on the 1.0.3 range until you can.
- Can the optional-packages command be skipped or safely rerun in CI and container builds?
- The optional-packages step is intended to be run interactively, and in environments without a /dev/tty you should invoke it manually rather than expecting it to complete inside an unattended build. Because idempotency is not explicitly guaranteed, the safest pattern is to skip it in CI and image builds unless you have verified it reruns cleanly against your pinned versions. Also make sure any code-style packages it pulls in land as dev dependencies only, so they do not bloat production images.
- Why were all my users logged out after upgrading to v2?
- Version 2.0.0 changes the default session serialization to JSON, which invalidates sessions created under the previous serialization format. The clean approach is a planned global logout or a blue-green cutover so the invalidation happens at a controlled moment. If you need a temporary bridge, setting SESSION_SERIALIZATION=php keeps existing sessions readable while you schedule the real cutover.
- Does the starter kit work with Pest 4, PHPUnit 12, and Vite 7?
- Yes, the v2 dependency stack moves to Pest 4 with PHPUnit 12 and to Vite 7 paired with laravel-vite-plugin ^2.0, so your frontend build pipeline must meet the Node and toolchain floors those versions require. Check your Node version in CI and local tooling before scaffolding, since an older Node runtime will break the asset build even though the PHP side is fine. Pest 4 also means reviewing any custom test helpers or plugins for compatibility with the new major.
- Can I add this starter kit to an existing Laravel application?
- It is designed as scaffolding for greenfield Laravel 13 projects, not as an installable runtime package, so retrofitting it into an existing application is a manual port rather than a Composer install. The Laravel 12 to 13 break, the ArtisanPack UI major alignment, and the Vite 7 rebuild make it a poor fit for a mixed-version estate. If you want the layouts and auth screens in an existing app, plan to copy and adapt the components deliberately.
- How is the starter kit maintained, and what are the alternatives?
- Maintenance effort is moderate to high because a starter kit that tracks Laravel majors forces periodic coordinated upgrades across PHP, Laravel, Vite, Pest, and the ArtisanPack UI suite. Expect this package to move in lockstep with Laravel releases rather than offering long independent support windows, so budget upgrade time alongside each Laravel major. If you do not want the ArtisanPack UI coupling, the official Laravel Livewire starter kit or a hand-rolled scaffold are the obvious alternatives to evaluate.
Weaver
How can I help you explore Laravel packages today?