Currently Available: Need a skilled Software Developer for your next project?
Categories
Laravel

Laravel Acquires Inertia.js

Laravel has acquired Inertia.js, as announced by Taylor Otwell at Laracon EU in Amsterdam this week. If you've built Laravel apps in the last few years, you've probably used Inertia - it's the tech that powers Jetstream and most modern Laravel + Vue applications. It lets you build single-page apps with Laravel while using React, Vue, or Svelte for your frontend.

How It Started

Back in 2019, Jonathan Reinink didn't want to split his app into a separate API and frontend just to use Vue or React. Instead, he built Inertia.js to let developers use these modern frameworks right inside their Laravel apps. The idea caught on - turns out lots of developers wanted this simpler approach instead of building complex API-based systems.

What's Changing

Not much, really. Laravel's team has already been heavily involved with Inertia, with Joe Tannenbaum leading the recent 2.0 release. The acquisition just makes it official. Jonathan Reinink isn't going anywhere - he'll still advise on the project.

What's Next

Laravel is building Inertia support right into their new starter kits. Whether you want to use React, Vue, or something else, there's a pre-configured setup ready to go.

What This Means

For developers using Inertia, this means the library will keep getting better, now with Laravel's full team behind it. The code stays free and open source - it's just officially part of Laravel now. For anyone building Laravel apps, Inertia remains a solid choice for adding a modern frontend to your application.

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

Subscribe to my newsletter

Get new posts when I publish them.

I respect your privacy. Unsubscribe at any time.

Leave a Reply

Your email address will not be published. Required fields are marked *