Laravel 11 Skeleton: What We Know So Far

There's a new Laravel 11 version coming in February 2024. Let's start preparing for some of the changes.

Links mentioned in the video:

- - - - -
Support the channel by checking out my products:

- - - - -
Other places to follow:

[JoseHenrique-xglp]

It wouldn't kill to have flags --slim and --classic. Something like that

[ROX]

Laravel 12 - return old style skeleton

[nathanmwamba]

Tailor Otwell, must create two types of projects installation for Laravel 11 full pack and normal pack but by default it should be full pack, otherwise new learners of Laravel will find it difficulty to start the process again of installing those packages one by one. Please!

[SXsoft]

I think some of the initial scaffolding(directory structuring) was very useful, many devs especially new one don't actually know how and where to group their classes to keep things clean
The initial hidden config files i feel is a bad move, hides a lot of things
I do understand having an "on demand add things" mentality but at least some core parts of the project should not be hidden
The problem i saw with many devs is NOT READING THE DOCUMENTATION, now you need to dig a bit deeper to know about some things

[cardboarddignity]

Next change: remove providers & controllers logic. To enable it back again, use 15 new console commands. Actually, what I feel, is that it drifts a bit to the subscription version a bit. Won't be surprised that Laravel 12 will have a free version with minimal functionality and "Enterprise" version with all the stuff.

[JJJMMM]

I don't love the hiding of configuration files and features. For new developers having the configuration options and features out there in the open is great for discoverability. Sure, it's more clutter, but that never bothered me. Seeing Exceptions\Handler.php and realizing you can easily control how exceptions are handled is great. Having to dig around the docs, Google or Laracasts isn't great.

But I'm not sure how significant the change is in practice. I'd guess that new users will probably install a starter kit. And I could see Laravel major version migrations being a bit simpler going forward.

[drtoxiccookie]

I acutal think this is an amazing change for laravel framework.

It's going to really help new people starting outwith laravel as its less scare with loads of confusing stuff that might not be need for basic website.

[KastsEcho]

To be fair, there was already push back when Taylor initially tried to push the slim skeleton on 10.x last May.

[maxshaian]

I personally find the changes logical. In a real project development many of these files were changed rarely and not from the very beginning, only when needed.
Now our eyes will not be destructed by the files you're not supposed to touch (yet).
The only additional hard skill we need to have is the understanding that you can publish config files, and the fact that routes, exceptions etc logic can be booted in the bootstrap file (again, if the logic is growing, you can extract it into a separate file and call it in the bootstrap.

[albinopepegas]

I like the new structure actually. Looks less bloated

[Buscalia]

I'll be very grateful if in the install there are an option like 'with old structure'.

[maikel]

I like it! Some of the files that are now being removed, I've never touched before. Less files means more overview, quite a few tutorials will probably need to be rewritten though, in order to let the user know they need to publish a certain file.

Either way, I'm all for it. Our biggest project is working with self created packages for full modularity anyway. So I'll probably just create a new Laravel 11 project, load those packages via composer and be done with it (aside from, perhaps upgrading the packages themselves, where necessary).

[VERone]

Would Laravel be like this back then when started it would either made me quit early or rewriting stuff already there only because I didn’t knew they were there in the first place

[vNYCblade]

i think this is a bad change... i understand that for some small API based projects the Slim skeleton makes sense, but for most people using the MONOLITH structure and using Inertia or Blade components or whatever it doesnt make sense to have to execute a TON of additional commands to publish each individual config file and then install api and this and that...WHY???
They way i see it, there should be 2 Scaffoldings in Laravel... one is default one that publishes everything as was done always, and the other would be something like *laravel new ---scaffold=slim* which would give you this Slim structure... That makes more sense to me as a dev...

[hentype]

I'm waiting for this for my new personal project.

[williamsernesto]

When installing api could you set that you want to use laravel passport?

[Diego-ebwe]

Very cool for new projects, but im not sure how hard it will be to migrate old projects to this.

[techfuture-code-tv]

when is release for production, A blog project with authentication tutorial will be much appreciated sir

[MrDragos]

More changes for the sake of changing stuff and pushing a new release. A lof of the "removed" files where in folders already so as much as you did not open those folder the files were hidden already.
I started on Laravel 7 and it was soo easy to work with. Now it seems the dificulty level was increased just for the sake of it, no specific reason. Why keep it easy when you can make it complicated and rise the level ?

[fuskydon]

Am very happy am the first person to like Laravel Daily video this morning
Yeah I know it's childish, don't mind me 😂