Since Laravel 11 introduced the new minimal application structure

[wattskenneth043]

Laravel Version

11

PHP Version

8.3

Database Driver & Version

No response

Description

Since Laravel 11 introduced the new minimal application structure, some important files and configuration entry points — such as app/Http/Kernel.php, app/Console/Kernel.php, and even some logic inside bootstrap/app.php — were removed or significantly changed.

While this new minimal setup looks clean, it causes serious issues during framework upgrades or when developers add custom logic in the bootstrap directory.

Steps To Reproduce

In previous versions (up to Laravel 10), developers could easily:

• Customize the HTTP or Console Kernel behavior.
• Add global middleware.
• Extend bootstrap logic (for custom environment setup or service loading).

However, with Laravel 11:

1. The Kernel classes are no longer part of the app skeleton.
2. If a developer adds or modifies files in the bootstrap/ directory, those changes can be lost or overwritten during upgrades.
3. There is no clear documented upgrade-safe way to inject custom bootstrap logic or restore the old Kernel behavior.

This leads to confusion and potential project instability for teams upgrading from Laravel 10 to 11.

• Laravel should keep an upgrade-safe bootstrap mechanism where developers can register custom logic.
• The framework should not overwrite or remove developer-defined files under bootstrap/ during updates.
• Documentation should include a clear migration path for projects that rely on Kernel customization.

---

Possible Solutions

1. Provide a bootstrap/custom.php file (or similar) that is ignored by the updater, meant for developer-defined bootstrap logic.
2. Add an official "Classic Kernel Mode" option that restores the old app/Http/Kernel.php and app/Console/Kernel.php behavior.
3. Update the documentation with detailed migration guidance on how to safely port old middleware and exception handling logic.

---

Environment

• Laravel Version: 11.x
• PHP Version: 8.2 / 8.3
• OS: Linux / macOS / Windows
• Type of App: API / Web App / SaaS

---

Summary

Laravel 11’s minimal structure is great for small or fresh projects, but it unintentionally breaks customization patterns used by many production-grade apps.

It would be helpful if the Laravel core team could introduce an upgrade-safe customization point or document the new best practice for advanced bootstrap and kernel overrides.

Thanks for your amazing work maintaining Laravel — this change just needs a bit more clarity and stability for developers upgrading from older versions.

[macropay-solutions]

From our knowledge the old way still works except the middleware part. There are ways to handle the middlewares in the new structure but you need to read the docs on how to do it. For deleting the files on upgrade that is news to us...

We did not like this change either so we were forced to do something radical.

[hctorres02]

Many of the behaviors defined as global are, in some sense, specific behaviors. For middleware, you can define them directly in the routes, either grouped or individually.

Can you give an example of how to use a bootstrap/custom.php file?

[hctorres02]

I understand where you're coming from, but using older versions isn't recommended. Of course, familiarity with older versions is a constant, but it's necessary to evolve. And the documentation has an excellent upgrade guide; I don't understand why there's resistance to such upgrades.

[macropay-solutions]

Each upgrade costs time and time is money. Not to mention potential bugs. You know that saying: "If it works, don't change it!".
So if we don't need the new stuff, why upgrade?
MIT is a "license to kill" in the hands of the developers that do changes to the framework.
If you blindly put your trust in them you face the consequences. It it not a blame, it is just the reality. That is why we took a radical decision to support our own fork and upgrade it to php 8.4 which for now is all we need.

PS. In that fork we fixed a "gazillion" bugs not fixed in the framework, the most dangerous being: #51825

[hctorres02]

My honest opinion: take the time necessary to learn what the upgrade guide says. Unfortunately (or fortunately), your request won't be granted, as this will have many implications.

Furthermore, Laravel's vision is to deliver something ready in just a few steps, and as of version 11, that's guaranteed. The necessary configurations are there. The famous plug-and-play.

[macropay-solutions]

@hctorres02 no one is blaming them. That is their business need. We respect that. Also we thank them for offering such a great framework. We on the other hand try to help as much as possible.

[macropay-solutions]

@hctorres02 we made no request. We did not open this issue/discussion.