Modernizing the Laravel Ecosystem: From Jetstream 2.0 to Spark Next

Refining the Starter Kit Experience

Laravel recently pushed

Jetstream 2.0
to production, marking a significant shift in how the framework handles authentication views. The biggest change involves the
Inertia.js
 stack. While the initial release utilized
Blade
 for login and registration to avoid duplication, the community demanded a more unified
Vue.js
 experience. Jetstream 2.0 delivers this by rewriting all authentication views as native Vue pages. Beyond the UI, team management received a vital upgrade: developers can now invite users who don't yet have an account via email, removing a major friction point in the user onboarding flow.

Collaborative Infrastructure with Forge Circles

For teams managing infrastructure,

Laravel Forge
introduced a long-awaited update to its Circle feature. Historically, only the circle owner could provision new hardware. The latest update allows members to create servers directly within a shared credential, such as
DigitalOcean
 or
AWS
. This delegation of power transforms Forge Circles from a simple viewing gallery into a true collaborative tool for DevOps teams.

The Evolution of Spark and Billing

Laravel Spark
is undergoing a total architectural pivot. To simplify the tool, non-billing features like API management and two-factor authentication were moved into Jetstream and open-sourced for free. The upcoming Spark release focuses exclusively on subscription billing. Taking inspiration from the
Stripe
 billing portal, the new Spark operates as an isolated panel with its own assets. This decoupling means Spark no longer dictates your application's CSS or JavaScript choices; it ships its own
Tailwind CSS
 and Vue files that remain separate from your main application layout.

Future Considerations for React SPAs

Taylor Otwell
is currently weighing the release of a
Next.js
 and
React
 starter kit. This potential tool would offer a canonical example of a Single Page Application (SPA) authenticating with
Laravel Sanctum
. While the demand for such a template is high, the decision is complicated by previous community confusion regarding the necessity of starter kits. The goal remains providing a clear path for modern frontend integration without imposing rigid opinions on the core framework.

2 min read