Laravel is NO LONGER *only* a PHP Framework

I'm going to give you my reasons why I consider Laravel to no longer be just a backend framework, that is, a PHP framework, but something more. We're going to talk a little about that something more, which I believe is more consolidated in the sense of consolidating, because consolidated is a video game console. In the latest versions we have, it's Laravel 12, specifically, since we have two important changes there, which are the ones I want to tell you about in this post.

So, basically, that's it. To tell you what I mean by this, which you're probably more or less assuming, we're going to go here to a console, a terminal, and type:

$ laravel new test

Note that from the root of the base the options we have:

○ None                                                     
○ React                                                    
● Vue                                                      
○ Livewire   

Note that if we simply want a pure installation, that is, with Laravel, meaning only the framework in the backend, simply PHP, regardless, we only have one option called none, but the others are already hybrid.

Laravel the full-stack framework - Frontend and Backend in one place

Above all, these two, React and Vue, will surely provide more options in the future, I don't know.

In Laravel 11 and later the options were not so direct

Since in older versions or older versions like 12 or earlier, for example 11, in order for you to create a project in this case in vi, since I re-created it with it, you had to first write, look, you want a project with Jetstream, which here, remember that a little bit of what I had told you that I had killed it, but here it is, as they say, from the root, from there. Therefore, I think this is a little more than simply a sense, that is to say, this is not only a way, but as they say, they are indicating to you that this is already part of the framework, that is to say, they have finished embedding it, they have finished integrating it, however you want to see it. More than simply a philosophy, it is already a fact, so to speak. It is no longer simply an option. It is already part of the framework, so to speak, even though they are secondary technologies, that is, technologies independent of Laravel. Therefore, precisely here, as you can see, when you go to create a Laravel project, you already have practically everything covered, not only what is on the server with Laravel with all the options that are great.

Here we can also Take advantage of all the features that we have in this type of client-side frameworks, that is, in the frontend. Therefore, that was what I wanted to comment on, which was a little bit of the indication that I was indicating to you before. Here we already have everything integrated, we already have the back end and we also have the front end. We already have everything in one place.

Laravel is unique, all integrated into a single project

This is a feature that I really believe is what differentiates or is the fundamental difference that we have in Laravel with any other framework, for example Django Flask etc., in order for you to be able to do this communication, which in this case we already have it from the root, you have to either use the CDN if it allows it, for example in the case of Vue, or you directly have to create a RestAPI or similar to consume the RestAPI that you have to create from the project, either in React or Vue. Another important point there is that in that case you have to have two projects, one is in Django Flask or whatever and the other is the native project in node or similar technologies, therefore they would be two projects. Here we simply have one, we have everything integrated, but that integration goes much further since again it is not simply a RestAPI but it is already integrated, excuse the redundancy, here so many times that I have said integrated into the blessed framework, which is the beauty of all this, and again it is appearing here in your face, it is indicating it to you here, in the case of iw. We also have a little bit of a hybrid I would see it between pure Laravel with these two since here

Livewire, the not-so-pure Laravel but not-so-fullstack version either.

Remember that we also have Alpine, so there we also have a pretty good integration because we also have lward account. Remember that it has many features to communicate directly with Alpine apart from also with vanilla js, so there we also have that integration, but it is a little bit, as they say, more timid, a little bit of Laravel, as they say, without straying so far from the Laravel approach, but we have additional features, which I think is excellent.

Inertia is not just a Vue project

Here what I was telling you, notice that this is directly a normal project in vio without many changes here it is using Api composition, the imports define its procs, the template part and it really is pure Vue but notice that they have made changes in this in this case it is to add TypeScript so what I mean by this is that if you check or compare what is the packet pun json for what are the dependencies in the front with the compuser pun Jason for what are the dependencies in the packing, understand here we have larel and here we have Vue read or whatever you are using, look at the number of plugins that we have here therefore it is something that you can see that they are, so to speak, worrying quite a bit about also polishing what we have in the frontend so that the integration is, so to speak, as clean as possible, as professional as possible and so that it really seems like it is a robust integration for Laravel and it is not something as superficial as it seemed that we had before simply because of those two small changes or at least in my opinion I see it like this again it was the options in the menu to create it and that this was simply a project with View that we had there but now this looks much more integrated again look at the amount of pluses that we have here not only View we also have TypeScript which is a bit like who says here also the novelty is that you can use it optionally if you don't want to use it you simply remove it but here it gives you all of that configured therefore again it is giving you not only a basic project in View but it is giving you a fairly robust project in Vue and they are indicating to you that look at all this integration that you have here you can use it 100% with Laravel So that was all I wanted to tell you in this video and of course I read the comments in which I would love to know your opinion