FrameworkBundle

FrameworkBundle is the glue that turns Symfony’s individual components — HttpKernel, Routing, DependencyInjection, Console, and more — into the cohesive “Symfony full-stack framework” that application skeletons like symfony/skeleton and symfony/website-skeleton are built on. It provides the application Kernel, registers the default console commands, cache warmers, and error handling, and exposes the top-level framework: configuration that every Symfony app’s config/packages/framework.yaml targets.

What You Get

• The application Kernel class and MicroKernelTrait for building single-class Symfony apps
• Controller resolution and argument-resolving integration between HttpKernel and your controller classes
• Built-in console commands (cache:clear, debug:router, debug:container, about, etc.) via Command/
• Cache warmers (CacheWarmer/) that precompute routing, container, and annotation caches for production
• A DataCollector/profiler integration and a KernelBrowser/Test toolkit for Symfony’s functional testing helpers
• Centralized framework: YAML/PHP configuration covering HTTP cache, secrets, translation, routing, and session behavior

Common Use Cases

• Bootstrapping a new full-stack Symfony web application via symfony/skeleton, which depends on FrameworkBundle to provide the Kernel and core services
• Configuring production performance behavior (HTTP cache, cache warmers, secrets vault) through the single framework: config key
• Writing functional tests against controllers using the bundle’s KernelBrowser and WebTestCase integration
• Debugging routing, container services, or configuration via the bundled debug:* console commands

Under The Hood

Architecture — FrameworkBundle.php is the bundle entry point; Kernel/ supplies the MicroKernelTrait that composes routing and container configuration inline for micro-apps, while DependencyInjection/ holds the (very large) Configuration class defining the entire framework: config tree and the compiler passes that wire HttpKernel, Routing, and other components together at container-compile time; Controller/, EventListener/, and ErrorHandler/ integrate controller resolution, kernel request/response events, and error rendering. Tech Stack — PHP 8.4.1+, depending on a wide slice of Symfony 8.1 components (http-kernel, dependency-injection, routing, event-dispatcher, cache, config) with require-dev covering optional integrations (Doctrine persistence, dragonmantank/cron-expression, asset mapper, translation extractors) exercised in CI but not required at runtime. Code Quality — An extensive Tests/ tree mirrors nearly every top-level directory (Kernel, Controller, CacheWarmer, DataCollector, Routing), and the bundle is maintained by 897 contributors with a well-established release/support-window process, evidenced by very active, consistent commit history. API Design — Nearly all app-facing behavior is opt-in/declarative through YAML or PHP config under framework:, keeping the imperative surface (mainly the Kernel/MicroKernelTrait) minimal — a strength for a component this central, though the full configuration surface is large and takes time to learn in depth.