React.js with Inertia in Laravel: Practical Example

[@DilovanMatini]

RILT has been my choice since the beginning of this year. Our team is completely comfortable with this stack. Even if the project needs a mobile, the APIs are almost ready.

[@angelp11]

Great video, always thanks for sharing your Laravel knowledge.

[@shmuelbisberg4396]

There are breaking changes in Inertia 2! As the release docs say, "All reload requests are now async by default." Now, you'll need to use Promises on the JS side. In addition, previously, requests were made one at a time; now, a couple can be made at the same time, so if you have a search bar that sends a request based on user input or anything like that, if you want to handle it "the right way," you'll need to keep a cancel token since the latest response is not guaranteed to come at the latest. And these bugs are the worst...

[@AlexGuinot]

I use RILT stack mainly because in the past I tried React in some college projects, so it felt natural and easy to use it with Inertia. In the end it depends about the developer experience :)

[@romedreba1587]

Vue is just popular because Taylor pushed it. There is not really any reason to choose VILT over RILT unless its a single developer project, but even then, the React ecosystem comes out on top. I get that Vue might resemble blade a bit more, but hiring, leveraging packages and libraries etc. are all reasons why RILT > VILT.

[@mihaes7172]

More on this, being asked about the new Laravel Cloud service implementation, Taylor's response was Inertia & React, reasoning that on React the package options are larger, kind of surprising answer

[@oretasletters]

Vue js is awesome, React is overwhelming for a new developer 🙂

[@AliHassan-v3k1v]

I hope you are doing unit testing for the project

[@angelp11]

What about the data interfaces? Most of react developers choose TypeScript to build apps, and one of the most disgusting things it's the typing of models/data. This approach could be great, but I don't know if there are something great with TypeScript also.

[@piotrpopawski6870]

Is this ready for commercial use?

[@LaravelDaily]

Why not? What is your definition of "ready"?

[@piotrpopawski6870]

@ pretty secured, Im making a webshop for a customer at the moment and the whole API work was just not enjoyable, now I saw your video i was wondering if I cloud use inertia and react instead

[@LaravelDaily]

Well it's pretty secured, at least it's on the market for ~5 years or so

[@the-fmk]

I prefer neither react nor livewire, but vue

[@greekapostle4548]

Missed angular

[@sntlln93]

Using Laravel+React with Inertia felt kinda awkward to be honest because I'm very comfortable using file based routing in react. If I have a backoffice i would simply have a js SPA (with vite of course) inside Laravel's resources folder and if i need SEO like features i would simply put my laravel backend and a remix/next frontend inside a monorepo and use git submodules and docker to manage it.

[@haniramadhan678]

Second

[@jaycarter592]

First again, lol