All 7 Namespaces & Autoloading questions
More in Namespaces & Autoloading
What is a namespace in PHP, and what problem does it solve when working with larger applications or third party libraries? How do you use the use keyword to import a class from a specific namespace, letting you reference it by its short name within a file? What is the difference between using a relative namespace reference, a fully qualified name starting with a backslash, and importing a class with use, when referencing a class from within a namespaced file? How do you organize namespaces effectively in a larger application to reflect logical groupings such as models, services, and controllers? How does Composer's classmap and files autoloading mechanism differ from PSR-4, and when would you use these alternative approaches instead? How does Composer generate and optimize its autoloader for production, and what is the difference between the development autoloader and an optimized production autoloader?
Advertisement
Back to results for “Namespaces”
PHP › Namespaces & Autoloading

How does PSR-4 autoloading work, and how does it map a namespace structure directly to a corresponding directory structure on disk?

Intermediate

Answer

PSR-4 is a widely adopted autoloading standard that establishes a direct correspondence between a class's namespace and its physical file location, meaning a class named App\Services\Mailer, when properly configured, is automatically expected to exist at a file path like src/Services/Mailer.php relative to a base directory associated with the App namespace prefix, and Composer's autoloader uses this exact convention to automatically locate and load the correct file whenever a class is referenced, without any manual require statements.
// composer.json
{
  "autoload": {
    "psr-4": {"App\\": "src/"}
  }
}
// App\Services\Mailer maps to src/Services/Mailer.php
Real-world example A developer adding a new Mailer class to the Services folder within their project's source directory can immediately use that class anywhere in the application without writing any require statement, since Composer's PSR-4 autoloader automatically knows exactly where to find it based purely on its namespace.

Common follow-ups: What happens if a class's actual file location does not match what PSR-4 expects based on its namespace?;How do you regenerate the autoloader after adding new classes or changing the autoload configuration?

Composer;Package Development & Publishing with Composer
All 7 Namespaces & Autoloading questions