- Is m6web/http-kernel-bundle compatible with Laravel?
- No. m6web/http-kernel-bundle is a Symfony bundle built around Symfony's Bundle class and FrameworkBundle; Laravel has no bundle system and uses Symfony components directly through Illuminate\Foundation\Http\Kernel. There is no supported integration seam, so it cannot be dropped into a Laravel application. Treat it as incompatible rather than as a Laravel package.
- Can I install m6web/http-kernel-bundle with Composer in a Laravel project?
- Installing it would only add files; it would not wire into Laravel's kernel or middleware pipeline. Its stale symfony/http-kernel constraints are also likely to conflict with the Symfony components in a modern Laravel dependency tree. Even a successful composer require would leave you with dead code and dependency risk, not working HTTP kernel behavior.
- What does m6web/http-kernel-bundle actually do?
- It is a lightweight Symfony bundle that extends the framework's HTTP kernel layer with a custom kernel, event-driven hooks around requests and responses, reusable listeners, and standard Symfony DI service wiring. It was designed to standardize kernel behavior across Symfony applications while staying close to Symfony conventions. It does not provide Laravel service providers, middleware, or facades.
- Is m6web/http-kernel-bundle still maintained?
- No. The repository is deprecated and archived, with the last release dated 2020-03-16. It has roughly 3 stars and 0 dependents, so there is no ecosystem validation or active maintenance. Archived request-handling code will not receive security patches.
- Does m6web/http-kernel-bundle support PHP 8 and Symfony 6 or 7?
- The last release predates PHP 8 and the Symfony 5.x, 6.x, and 7.x lines, so assume PHP 7.x-era and Symfony 3/4 constraints. Check its composer.json for exact ranges before planning anything. If the constraints are pre-PHP 8, the code will not parse cleanly on supported runtimes without edits. It is not a viable dependency for modern Symfony or Laravel stacks.
- What should Laravel developers use instead of m6web/http-kernel-bundle?
- Use Laravel's native extension points: HTTP middleware, terminable middleware, service providers, Application::bootstrap(), events, and a custom implementation of Illuminate\Contracts\Http\Kernel if you truly need kernel-level behavior. These cover request transformation, response post-processing, exception handling, and cross-cutting concerns without a third-party kernel bundle. No replacement Composer package is required.
- How do I migrate behavior from m6web/http-kernel-bundle to Laravel?
- First inventory usage by grepping composer.json, composer.lock, and code for the package name and any forked kernel class. Extract the custom kernel into a scratch branch and annotate each overridden method, then map those behaviors to Laravel middleware, bootstrap logic, events, or a custom kernel. Write characterization tests against the old behavior, implement the native replacement, and remove the dependency in the same pull request once tests pass.
- Does m6web/http-kernel-bundle work with Laravel's HTTP kernel or middleware pipeline?
- No. Laravel's HTTP kernel is Illuminate\Foundation\Http\Kernel, and its middleware pipeline is not the Symfony bundle kernel lifecycle this package targets. The package's PSR-7/PSR-15 middleware-based kernel does not plug into Laravel's kernel registration or bundle configuration. You would have to rewrite it as Laravel middleware plus a service provider, which is a port rather than an integration.
- What are the production and security risks of using m6web/http-kernel-bundle?
- The package is archived and its request-handling layer is the highest-blast-radius surface in a web application, so unpatched vulnerabilities would go unfixed. It also drags stale symfony/http-kernel constraints into the dependency graph and can block upgrades. The safer path is to rebuild any needed behavior natively and avoid adding it to production composer.json.
- How can I check whether my codebase depends on m6web/http-kernel-bundle?
- Search composer.json and composer.lock for m6web/http-kernel-bundle, then grep application code for the bundle class name and any custom kernel subclass that extends it. Because the package has 0 public dependents, removal is usually cheap. If you find internal usage, gate removal on a native replacement passing characterization tests.