What’s New in Laravel 11: Upcoming Features and Updates

Quick Summary:

Table of Contents

Laravel 11 Release Date

Referring to the latest update on the official website of Laravel, the Support Policy mentions that the latest version of Laravel 11 release date is on February 6, 2024, as we know that the Laravel core team follows the Semantic Versioning methodology that entails that the major updates to the framework are released once a year during the first quarter. However, it doesn’t mean your existing applications should be updated immediately to the latest Laravel version.

The Laravel framework was last released (LTS or Long Term Support) in version 6, but each major version possesses two years of updates; this enables enough time to get your existing codebase in check and upgrade it accordingly. According to the official Laravel documentation, Laravel 10 will receive bug fixes until August 6, 2024, and security fixes until February 4, 2025.

What’s New in Laravel 11: Latest Features and Updates

The team at Laravel understands the importance of the latest features and updates being introduced within the system. However, they strive to deliver the best to the developers and the business owners. This is why using the latest version of the framework or its components is always preferred. The same is the case with the latest Laravel v11, which has many updates that can benefit your business under several heads. Let’s proceed with what Laravel 11 has with this year’s latest updates.

No Support For PHP 8.1 in Laravel 11

The first and foremost change that Laravel version 11 will bring is dropping the support for PHP 8.1. The reason is that the PHP 8.2 will be fully established when Laravel 11 is up for use, and the PHP 8.3 will also be stable. Therefore, with 2 upgraded versions running within the market, the need for an older version, PHP 8.1, is unnecessary. However, again, it is not a mandate to upgrade to the latest version instantly, but you can take a thorough testing approach. You can update the existing applications gradually, but upgrading to the latest version is a great choice.

More Minimalistic Application Skeleton

Laravel 11 possesses a slimmer application skeleton. The intent here is to involve less boilerplate code to deal with. This approach will benefit the business owners and developers to deal with less code, leading to faster development. Talking about the changes made in-depth, they are all as follows:

• Within the ‘AuthServiceProvider,’ the ‘$policies’ are removed as the framework discovers them automatically.
• In the ‘EventServiceProvider,’ the ‘SendEmailVerificationNotification’ is no longer necessary, as the base ‘EventServiceProvider’ is registering it. Also, you will notice that the auto-event discovery is now enabled by default.
• ‘BroadcastServiceProvider’ is not needed anymore and, therefore, is removed. The framework is not automatically loading the routes/channels.php file.
• ‘RedirectIfAuthenticated’ is simpler due to the base one in the framework’s internals.
• The ‘Authenticate’ middleware now does not call the ‘redirectTo()’ for the JSON routes, thereby removing the unnecessary ternary checks.
• All the ‘EncryptCookies,’ ‘PreventRequestsDuringMaintenance.php,’ ‘TrimStrings,’ ‘TrustHosts,’ ‘TrustProxies,’ ‘ValidateCsrfToken’ and ‘ValidateSignature’ middleware are removed from the skeleton structure.
• The Custom Artisan is loaded automatically with Laravel 11, and the console does not need to call the ‘load()’ method.
• The routes/console.php have been removed. The closure-based artisan commands can now be registered in the console kernel only.
• Various other migrations are either consolidated into a single file or removed.
• The ‘AuthorizesRequests’ and ‘ValidatesRequests’ traits have been removed from the base controller.
• The bootstrap/app.php file has been reduced in size, now with only three lines of code.
• The exception handler is also removed in the Laravel v11.

The New Dumpable Trait - (dump () and dd () from your objects)

The core intent behind this pull request is to replace the current dd and dump methods in most Laravel classes, and it will introduce a new Dumpable trait as well. Also, the trait enables Laravel users and package authors to include debugging methods easily within their class by utilizing this trait. Let us take a glimpse of an example to use it:

foo()->bar();
 
// After:
$address->foo()->dd()->bar();

Also, this pull request is specifically intended for Laravel 11.x as it requires modifications to the signature of several methods. For consistency across the entire codebase, adding the …$args to the debugging methods was added. However, it is still preferred for the Laravel 11.x version.

Model::casts() Method Live in Laravel 11

In the latest version of Laravel, Model casts are now defined as a method instead of a property. When defined as a method, it enables performing other things, such as calling other methods directly from the casts.

Generally, Laravel requires declaring attribute casting in an eloquent model as given below:

class User extends Model
{
    protected $casts = [
        'email_verified_at' => 'datetime',
    ];
}

However, with Laravel 11 you can easily define your casting through a ‘casts()’ methods in your model that offers you a chance to use static methods from class doing the casting as illustrated below:

class User extends Model
{
    protected function casts(): array
    {
        return [
            'foo' => AsCollection::using(FooCollection::class),
        ];
    }
}

Also, you can now specify your casts as an array, as given below:

class User extends Model
{
    // Even in the old $casts property!
    protected $casts = [
        'foo' => [AsCollection::class, FooCollection::class],
    ];
 
    protected function casts() : array
    {
        return [
            'foo' => [AsCollection::class, FooCollection::class],
        ];
    }
}

The ‘casts()’ method is prioritized over the ‘$casts’ property.

Also, these changes are non-breaking, which will not affect the current code when you upgrade to Laravel 11.

Config Changes

The older versions of Laravel possessed multiple config files, and Laravel v11 has come up with these files removed and all the config options being cascaded down. The ‘.env’ has been expanded to include all the options you want to set or configure.

Further, pairing with Laravel 11 comes with a completely new ‘config:publish’ command that enables you to bring back any config that you need. And, even after bringing them back, the new cascade feature enables you to remove every option you don’t want to customize, thereby ensuring a more streamlined and tailored configuration experience. Considering a common example, running ‘artisan config:publish database‘ generates a dedicated database config. File, precision, and organization at ease.

// To publish all the config files
php artisan config:publish

// Specific config file
php artisan config:publish database

Slimmed Default Migrations

In Laravel v11, when creating a new Laravel application, the default migrations from 2014 and 2019 will undergo a significant reorganization. Instead of being spread across multiple migration files, these migrations will be consolidated into two files only.

This will allow the developers initiating a new Laravel project to have a cleaner and more streamlined database/migrations directory, enhancing the overall development experience and project maintainability.

Console Kernel (Removed)

After removing the HTTP Kernel, the Console Kernel is also removed, and in place of that, a new approach is introduced. That means in place of having a dedicated Console Kernel file, developers will be responsible for defining their console commands directly in the routes/console.php file.

The routes/console.php file traditionally defined the Artisan commands as closures will now work as the primary location for registering all console commands. This change aims to simplify the structure of Laravel applications and offer a more simplified and consolidated way to manage console commands. By removing the Console Kernel and moving the command definitions to routes.console.php, Laravel aims to streamline the application’s configuration and reduce unnecessary files. This new approach enables the developers to have a clear and centralized view of all the console commands, making it easier to manage and maintain them throughout the development process.

Routes Related Changes

Considering the default setting in Laravel, there will be two route files: console.php and web.php. If you wish API routes to be included, you must opt-in by running the ‘php artisan install:api’ that will offer you the API routes file and the Laravel Sanctum functionality.

Similarly, for the websocket broadcasting, you can use the command ‘php artisan install:broadcasting.’ This command will set up the necessary files and configurations crucial for the websocket broadcasting in your Laravel applications. Collectively, these changes will contribute to a radical shift towards a more modular and customizable application structure.

Other GitHub Pull Requests Hinting At the Latest Laravel 11 Features

Here is a list of the other probable Laravel 11 Features and Updates that we can expect in the latest version of Laravel 11.

How To Install Laravel 11

To install Laravel v11, initially, you must specify the ‘-dev flag’ during the installation. Laravel can then be programmed to download and install only the master branch from the ‘laravel/laravel’ repository.

Laravel new hello-world-dev

However, if you prefer the hands-on installation experience, then your go-to choice is a Composer.

composer create-project -prefer-dist laravel/laravel hello-world dev-master

Why Businesses Should Upgrade to Laravel 11?

There are several reasons why you should upgrade your existing Laravel application to the latest Laravel 11 version. As a trusted Laravel Development Partner, Bacancy strives to bring you the benefits of upgrading to the latest Laravel version 11. Let us have a look at it:

• Improved Performance: Get enhanced performance under the hood, faster routing, optimized database queries, or improved caching mechanisms, along with improved app performance with speed boost.
• Enhanced Developer Experience: Prioritizing the developer experience, Laravel 11 takes it to the next level with improved documentation, error handling, and debugging tools, delivering a smoother and more enjoyable development process. Collectively, this leads to faster development and more efficient results for your business.
• Multiple New Features and Tools: The latest Laravel version 11 introduces a number of new features and tools to simplify complex tasks. From enhanced authentication options to streamlined API development, Laravel 11 empowers your developers to build strong applications more efficiently, which benefits your project.
• Blade Templating Enhancements: Blade, the Laravel templating engine, gets some love in this release. It now offers even more flexibility and power for crafting beautiful reusable views for your application.
• Security Upgrades: Security plays a crucial role in every project regarding web development for businesses. Laravel 11 includes the best and most efficient security enhancements and best practices to help you protect your applications and data.
• Backward Compatibility: The most crucial factor that makes it ideal for businesses to shift to the latest Laravel 11 version is the backward compatibility that ensures you can upgrade your existing Laravel applications to the latest Laravel v11 with minimal effort.

How To Become a Contributor To Laravel 11 Features and Bug Fixes?

If you are an expert in Laravel development, then you can easily give your valuable contribution to the Laravel community and fix the bugs that you have encountered working on your Laravel project, or you can also create and contribute an exceptional new feature in the upcoming version of Laravel v11. The steps to do the same are:

• Visit the Laravel 11 GitHub Page. There, the Pull Requests will help you know the bugs that are already fixed or the features that are already introduced.

Choose one bug or feature you believe is your pain point while working on your

• Laravel project, which you can resolve and create a solution that best suits your problem.
• Send the Pull Request over to the laravel/framework repository, collect feedback, improve, and get merged.

Note: It is essential to consider that if you really wish your feature of bug fix to be merged. Then, you must add something to the framework that is a win for developers but not a pain for the core team at Laravel or Taylor Otwell in the long run.

Conclusion