Livewire Starter Kit Laravel Package

Technical Evaluation

Architecture fit: This is a Laravel application starter kit / scaffolding package, not a runtime library. It is a strong fit for greenfield Laravel 13 applications that intend to adopt the ArtisanPack UI suite (accessibility, core, Livewire UI components, security) and want opinionated defaults for Vite, Pest, Tinker, and optional package installation. It is a poor fit for existing Laravel 12 applications that are not ready for a coordinated framework and dependency-major upgrade.

Integration feasibility: High for new applications already standardizing on PHP 8.3+ and Laravel 13. Low-to-moderate for existing applications because v2.0.0 drops Laravel 12 compatibility entirely. The laravel new non-interactive fallback improves developer experience, but teams must explicitly account for the “run this manually after install” path in automated provisioning.

Technical risk: High. This release stacks multiple breaking changes: minimum PHP moves to 8.3, Laravel 13 becomes mandatory, several companion dependencies take major bumps, Vite moves to 7, Pest moves to 4, and session serialization defaults to JSON, invalidating existing sessions. The dependency graph is also opinionated and tightly coupled to ArtisanPack UI majors, so upgrade risk is concentrated in a single starter-kit version rather than independently adoptable packages.

Key questions:

• What is the supported Laravel 13 and PHP 8.3/8.4/8.5 support window for this package?
• Does artisanpack-ui/security ^2.1.0 introduce its own breaking changes beyond the version bump?
• Is the optional-packages command idempotent, and can it be safely skipped or rerun in CI and container builds?
• What is the recommended v1 → v2 migration path for existing applications that cannot move to Laravel 13 immediately?
• Does the session serialization change require a coordinated logout, or can SESSION_SERIALIZATION=php be used temporarily as a bridge?
• What Node version and build pipeline constraints come with Vite 7 and laravel-vite-plugin ^2.0?

Integration Approach

Stack fit: Target stack is PHP 8.3–8.5, Laravel 13, Pest 4 / PHPUnit 12, Vite 7 with laravel-vite-plugin 2, and the ArtisanPack UI L13-ready majors. MySQL/MariaDB SSL CA handling is now compatible across PHP 8.3–8.5. This is a coherent stack for a new L13 application, but it is not a drop-in fit for a mixed-version estate.

Migration path: Use two tracks. For new applications, scaffold directly on v2.0.0 and accept the opinionated defaults. For existing Laravel 12 applications, either remain on the 1.0.3 compatibility range or perform a dedicated Laravel 13 upgrade branch first, then adopt v2.0.0. Do not attempt to combine the starter-kit major upgrade with unrelated feature work.

Compatibility: v2.x targets Laravel 13 only and PHP 8.3+. The previous ^12.0|^13.0 range is gone. Frontend tooling requires Vite 7 and the associated Node/toolchain floors. Session-compatible upgrades require a planned invalidation or an explicit temporary override to SESSION_SERIALIZATION=php.

Sequencing:

1. Pin CI and runtime images to PHP 8.3, 8.4, or 8.5 and remove PHP 8.2 jobs.
2. Upgrade Laravel to 13 and align laravel/tinker, laravel/boost, Pest, and PHPUnit before adopting the starter kit.
3. Upgrade ArtisanPack UI companion packages to their L13-ready majors and verify artisanpack-ui/security 2.1.0 behavior.
4. Rebuild the frontend on Vite 7 and laravel-vite-plugin 2.
5. Decide the session serialization rollout: planned global logout, blue/green cutover, or temporary SESSION_SERIALIZATION=php bridge.
6. Run the optional-packages command manually in environments where /dev/tty is unavailable, and ensure code-style packages are installed as dev dependencies only.
7. Smoke-test MySQL/MariaDB SSL connections on PHP 8.5.

Operational Impact

Maintenance: Moderate-to-high. A starter kit that tracks Laravel majors will force periodic coordinated upgrades across PHP, Laravel, Vite, Pest, and the ArtisanPack UI suite. Teams should expect this package to move in lockstep with framework releases rather than provide long-term backward compatibility.

Support: Clear support boundary: v2.x is Laravel 13 / PHP 8.3+ only; Laravel 12 users must stay on the 1.0.3 line. The non-interactive fallback is helpful, but support documentation should explicitly describe CI, container, and laravel new --no-interaction behavior.

Scaling: Scaling risk is low at the application-runtime level because this is scaffolding, but the session serialization change has fleet-wide impact. Any application with active sessions will force reauthentication or session loss unless a bridge or staged rollout is used.

Failure modes:

• CI or container builds hang or skip optional packages when no TTY is reachable.
• Session data is invalidated by the php → json serialization switch.
• PHP 8.5 emits deprecation notices if the SSL CA constant fallback is missed in custom database configs.
• Vite 7 / plugin 2 mismatch breaks frontend builds.
• Companion dependency majors introduce transitive breakage, particularly artisanpack-ui/security 2.1.0.
• Code-style packages leak into production if the partitioned composer require --dev behavior is bypassed.

Ramp-up: Moderate. Developers familiar with Laravel 12 will need orientation on Laravel 13 defaults, Vite 7, Pest 4, and the session serialization change. Platform and DevOps teams need to understand the TTY fallback and the manual post-install step. Overall ramp-up is manageable for a greenfield team but non-trivial for an organization maintaining multiple Laravel 12 applications.