- Can I install n7/symfony-http-bundle in a Laravel app with Composer?
- Composer can download it, but it will not behave like a normal Laravel package. The repository is a Symfony bundle that expects Symfony's bundle registry and HttpKernel boot process, neither of which exists in Laravel. To use it you must either extract the concrete service classes into a Laravel service provider or bridge a standalone Symfony ContainerBuilder. Do not assume composer require followed by auto-discovery will give you working Symfony HTTP semantics.
- How do I register n7/symfony-http-bundle in Laravel?
- In Symfony you add the bundle class to config/bundles.php and let the kernel boot it. Laravel has no registerBundles() hook, so there is nothing for the bundle to attach to. The practical route is a custom Laravel service provider that instantiates the bundle's service classes directly, or a scoped bridge that boots a ContainerBuilder and aliases services into Laravel's container. If the bundle class contains compiler passes or build() logic, audit it before dropping it.
- Is n7/symfony-http-bundle compatible with Laravel 10, 11, and 12?
- Laravel 11 and 12 ship Symfony 7.x components, while Laravel 10 sits on Symfony 6.x. Symfony bundles commonly pin symfony/http-kernel and symfony/http-client to ranges such as ^7.0, which will conflict on Laravel 10. Check the package's composer.json constraints for php, symfony/http-kernel, and symfony/http-client before committing. Symfony 8 will likely arrive before this package tracks it.
- What does n7/symfony-http-bundle actually do?
- It packages Symfony's HTTP layer, HttpFoundation and HttpKernel, into a reusable bundle with service definitions, an extension, and standard bundle configuration. The intent is to keep HTTP setup consistent across Symfony projects. Given the naming and description, it is likely a thin convenience layer over symfony/http-client decorators, middleware, retry, and logging. The Laravel bridging language in the overview should be treated as a claim to verify, not a guarantee.
- Can I use Symfony HttpFoundation requests and responses in Laravel with this package?
- Laravel's Illuminate\Http\Request already extends Symfony's Request, so basic HttpFoundation semantics are present without this package. What the package adds is container bindings, facades, and a Symfony-style kernel layer, which introduces a second abstraction alongside Laravel's routing and middleware. For most Laravel apps the conversion is unnecessary; for sharing code with Symfony, prefer extracting the concrete HTTP classes. Introducing a second request/response pipeline fragments observability and onboarding.
- How do I configure n7/symfony-http-bundle?
- In Symfony the bundle exposes an extension and config tree, configured through config/packages/*.yaml with normal config merging. Laravel does not have bundle-level config merging, so the publishable configuration from the overview must be mapped manually into Laravel's config files and service provider. Confirm which keys the extension actually reads before assuming the published file is complete. If you bridge a ContainerBuilder, you must replicate the same config semantics yourself.
- Is n7/symfony-http-bundle safe for production use?
- Treat it as high risk until audited. Public signals are thin: roughly 3 stars, 0 dependents, a single maintainer, and an overall score around 0.135, meaning no downstream project has validated it in production. Low download volume also means low scrutiny, so any CVE or Symfony version break becomes your incident. Vendor or fork the source, pin exact versions, and review the bundle, extension, and service definitions before production use.
- How do I test n7/symfony-http-bundle in a Laravel application?
- There is no clear evidence of a test suite that exercises the bundle against a real kernel. Write your own integration tests that boot the service provider or bridge and assert the container bindings resolve. If you extract the HTTP decorators, test them directly against a mocked Psr\Http\Client\ClientInterface. Also test failure paths such as retry and backoff, since those are the behaviors most likely to diverge from Laravel's Http facade.
- What are the best alternatives to n7/symfony-http-bundle?
- For HTTP calls in Laravel, use the built-in Http facade, which is Guzzle-backed and well documented. If you specifically want Symfony's client, install symfony/http-client directly and bind it to Psr\Http\Client\ClientInterface in a small service provider. For shared Symfony code, extract the decorator classes rather than adopting the bundle. A full Symfony application is the only clean option if you genuinely need HttpKernel semantics.
- Is n7/symfony-http-bundle actively maintained?
- All available signals point to low activity and a bus factor of one. With 3 stars and 0 dependents, there is little ecosystem pressure to keep it current with Symfony releases. Check the repository for recent commits and tagged releases before relying on it. If you adopt it, plan to fork and maintain the pieces you actually use.