Section 1.1: Updated PHP Version

Laravel 11 requires the use of PHP version 8.2 or higher, discontinuing support for PHP 8.1. This shift is not just a minor technical adjustment; it is a deliberate strategy to take advantage of enhancements and new functionalities offered by PHP 8.2, such as new return types, named arguments, and improved error handling. Additionally, the updated PHP specifications enhance application security, ensuring that Laravel projects benefit from the latest protective measures and efficiencies.

// Example code demonstrating new features in PHP 8.2

function exampleFunction(int|string $parameter): never|float {

if (is_string($parameter)) {

throw new Exception("Expected a number, received a string.");

}

return sqrt($parameter);

}

Section 1.2: Streamlined Application Scaffold

A standout feature of Laravel 11 is the considerable simplification of the application scaffold. The removal of directories like Console, Exceptions, and Http/Middleware, along with the elimination of the Http/Kernel.php file, represents a major restructuring. These components have been relocated deeper within the framework, with application configuration now handled through the bootstrap/app.php file. This change aims to simplify project structure and promote a more integrated configuration approach.

// Example of new configuration in bootstrap/app.php

return Application::configure(basePath: dirname(__DIR__))

->withProviders([...])

->withRouting([...])

->withMiddleware(function (Middleware $middleware) {

// Adding middleware here

})

->withExceptions(function (Exceptions $exceptions) {

// Handling exceptions here

})->create();

Section 2.1: Simplified Configuration

Laravel 11 has drastically redefined configuration management by eliminating all configuration files from the config directory. This move emphasizes the use of environment variables in the .env file, enabling developers to manage application settings in a more centralized and cohesive manner. While this may seem like a substantial change, Laravel 11 allows users to publish configuration files via the php artisan config:publish command, offering flexibility for customization.

# Command to publish configuration files

php artisan config:publish

# Command to publish a single configuration file

php artisan config:publish --tag=database

Section 2.2: Middleware Configuration Changes

The introduction of Laravel 11 brings essential changes in middleware configuration and management. With the removal of the app/Http/Kernel.php file, the responsibility for middleware configuration shifts to the bootstrap/app.php file. This transition necessitates that developers familiarize themselves with the new configuration system, fostering a more flexible approach to middleware management.

// Example of adding middleware in bootstrap/app.php

return Application::configure()

->withMiddleware(function (Middleware $middleware) {

$middleware->append(AppHttpMiddlewareMyMiddleware::class);

})->create();

Section 3.1: Model Casts Handling Innovations

Laravel 11 introduces a novel method for defining model casts, allowing them to be set using a method instead of a property. This change enhances flexibility, enabling developers to execute code within the casts' definitions, thereby making Laravel models even more expressive and adaptable.

// Example of model utilizing the casts() method

class User extends Model

{

protected function casts(): array

{

return [

'email_verified_at' => 'datetime',

'is_admin' => 'boolean',

];

}

}

Section 3.2: Database Tooling Improvements

With Laravel 11, a series of enhancements in database management tools have been introduced, particularly in migration handling. The framework now requires a more deliberate approach to modifying column definitions, moving away from the default behavior of retaining them. Additionally, Laravel 11 shifts from relying on Doctrine DBAL to utilizing its native solutions for database schema management, aiming to streamline the migration process.

// Migration example without retaining default column definitions

Schema::table('users', function (Blueprint $table) {

$table->string('name', 50)->change();

});

Section 4.1: New Helper Functions

Laravel 11 introduces several enhancements to facades and helpers, focusing on improving code readability. A notable addition is the new once helper, which facilitates function return value memoization. This ensures that a function is executed only once, regardless of how many times it is called, making it particularly useful for computationally expensive operations.

// Using the once helper for result memoization

$result = once(function () {

return complexCalculation();

});

Section 4.2: The Dumpable Trait

The new Dumpable trait in Laravel 11 can be utilized in any class to add dump and dd methods, enhancing debugging capabilities. This feature allows for more intuitive and rapid debugging, especially with complex data structures or when verifying an object's state during execution.

// Example of using the Dumpable trait in a class

class ExampleClass

{

use IlluminateSupportTraitsDumpable;

protected $data;

public function __construct($data)

{

$this->data = $data;

}

}

(new ExampleClass(['foo' => 'bar']))->dump();

Section 5.1: Changes in Routing Structure

Laravel 11 adopts a fresh approach to routing and API management, making the default routes/api.php and routes/channels.php files optional. Developers can restore these files using specific Artisan commands if they choose to implement API routes or broadcasting features. This alteration reflects Laravel's commitment to providing greater flexibility and a minimalist project structure.

# Command to restore the routes/api.php file

php artisan install:api

# Command to restore broadcasting functionality

php artisan install:broadcasting