Laravel 12: Changes Frustrating Long-Time Users

Laravel 12 isn't bringing huge features, but it's changing how the framework is packaged - and it's pissing off part of the community. Here's what's changing and why it matters.

Jetstream and Breeze Are Gone

Laravel ditched Jetstream and Breeze for new starter kits. Taylor Otwell explained on Laravel News they're going with "one starter kit per stack" - for React, Vue, and Livewire.

The thing is, Jetstream was actually good. It let developers choose Vue or Livewire, add team management if needed, and build on a solid foundation. It worked.

Jetstream is still available on GitHub and works with Laravel 12, but removing it from the docs is usually the first step before killing it off completely.

Chasing JavaScript Developers

These changes are clearly targeting JavaScript developers and bootcamp grads. The new kits use ShadCN UI for React/Vue and Flux for Livewire - trendy component libraries that React devs might like.

The problem? These new kits are more limiting. ShadCN locks you into specific styling patterns that Jetstream's Tailwind approach didn't. The Livewire kit pushes Flux with its paid "Pro" tier, which hasn't gone over well with everyone.

As one developer put it: "It used to be so easy... you could quickly scaffold auth and start building. Now it's way too complicated with Volt, Flux, no Jetstream, no Blade-only kit, mixing HTML/PHP/JS, etc."

It looks like Laravel is prioritizing new users over keeping existing ones happy.

Third-Party Services Everywhere

Laravel is also pushing more third-party services. The installer now promotes WorkOS for auth and social login. Yes, WorkOS has a free tier for up to 1 million users, but outsourcing core functionality like authentication feels wrong to many PHP developers.

"I just want my auth to be local… not having to rely on some third party," one developer wrote. This follows a pattern: Laravel Herd replacing Sail, Laravel Cloud replacing Forge, and now WorkOS instead of built-in auth.

Let's be honest - Laravel's venture capital funding probably has something to do with this push. The massive WorkOS banner on Laravel's homepage makes it pretty obvious where things are headed.

That New Website

Laravel's new website doesn't help matters. The homepage is full of unnecessary animations and scroll effects. Reddit discussions show a clear divide: some like the modern look, but others (including me) think it sacrifices function for flash.

The site now explicitly targets beginners: "If you're new to web development, Laravel's documentation, tutorials, starter kits, packages, and products will help you start quickly." That's fine, but what about the professionals who've been using Laravel for years?

The Core Still Works

Despite all this, Laravel's core is still solid. The architecture, ORM, and syntax that made it great haven't changed. You can still use Jetstream (for now) or roll your own auth. The community remains strong despite these frustrations.

The challenge for Laravel is finding balance. They clearly want new developers, but they risk alienating the experienced ones who made Laravel successful in the first place. One community member warned that Laravel might be "losing touch with the developers that helped raise the Laravel community."

Laravel could support both groups by maintaining Jetstream while offering simpler options for beginners. But it seems they've decided growth matters more than keeping existing users happy.

For now, Laravel developers have choices: adapt to the new direction, use Jetstream while it lasts, or look elsewhere. The next few months will tell us whether Laravel can grow without sacrificing what made it great.

The community clearly cares - that's why this debate is happening at all. Laravel matters to a lot of developers' careers. Whatever happens next, keeping that community engaged will determine Laravel's future success.

What I'm building

Delegate tasks. Get software.

Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.

Take a look at vroni.com