- Can I use incompass/injection-bundle in a Laravel application?
- No. incompass/injection-bundle is a Symfony bundle built around Symfony's kernel, bundle registration, DI extension, compiler passes, and cache warmup. Laravel has no equivalent extension points for loading a Symfony bundle, and there is no adapter that makes this package work inside a Laravel application. Using it in Laravel would require porting its scanning and definition-rewriting logic into a service provider, which is a rewrite rather than an integration.
- How do I install incompass/injection-bundle, and does it work with Composer in Laravel?
- The Composer package name is incompass/injection-bundle, but installing it in a Laravel project will not wire it into Laravel's container. It expects Symfony bundle registration in config/bundles.php plus Symfony's DI extension lifecycle. Composer may resolve the package, but Laravel will not load it as a bundle, so installation alone gives you no working integration.
- Does incompass/injection-bundle support Laravel 11 and Laravel 12?
- There is no declared Laravel support. The package targets Symfony's container and bundle lifecycle, so Laravel 11 and Laravel 12 are outside its compatibility surface. There is also no release history or documented PHP/Symfony version matrix to rely on. Treat it as unsupported for any Laravel version.
- Is there a Laravel adapter or bridge for incompass/injection-bundle?
- No Laravel adapter or bridge is provided. The package depends on Symfony-specific extension points such as compiler passes and bundle DI extensions, and Laravel does not expose those hooks. Any bridge would have to be custom-built and would effectively reimplement the bundle's behaviour inside a Laravel service provider.
- What does incompass/injection-bundle offer that Laravel's container does not?
- Nothing that Laravel needs for normal dependency injection. Laravel already resolves constructor dependencies automatically, supports contextual binding, and lets you bind interfaces to implementations with $this->app->bind() or singleton(). The bundle's value is a convention for declarative Symfony service wiring, which duplicates capabilities Laravel already has natively and with better IDE and type safety.
- How do I configure dependency injection in Laravel without this bundle?
- Use Laravel's service container directly. Type-hint dependencies in constructors, register bindings and singletons in a service provider such as AppServiceProvider, and use contextual binding when a class needs a specific implementation. For collection-style injection, use tagged bindings or explicit resolver logic in a provider rather than annotation scanning.
- Can I test services wired by incompass/injection-bundle in Laravel?
- You can test Laravel services normally with Laravel's testing helpers and the container. Because the bundle is not Laravel-native, there is no supported way to boot its Symfony compiler passes in a Laravel test suite. If you ported any wiring logic, test the resulting bindings through the container and mock dependencies at the boundary. Do not expect the bundle's own conventions to be exercised in Laravel tests.
- Is incompass/injection-bundle safe for production use in a Laravel app?
- It is not recommended for production in a Laravel app. The package has no observable maintainer cadence, release history, security-disclosure path, or CVE monitoring, and its licence and transitive dependencies are unverified. Dependency injection code touches every service in the container, so the blast radius is large while the benefit over Laravel's native container is negligible.
- Who maintains incompass/injection-bundle, and is it actively maintained?
- Maintenance is unclear. The package has zero stars, zero dependents, no tagged releases, and a single obscure vendor, Incompass, which is a CRM vendor rather than a dependency-injection tooling maintainer. There is no documented security-response process. Those signals make it a poor choice for a long-lived Laravel estate.
- What are the best alternatives to incompass/injection-bundle for Laravel?
- For Laravel, the alternative is the framework itself: constructor injection, bind/singleton/contextual binding in service providers, and interface-to-implementation maps. For Symfony projects, use native autowiring and PHP 8 attributes such as #[Autowire], #[Required], #[TaggedIterator], and #[AsDecorator]. Both approaches are core, type-safe, and IDE-navigable, so you do not need annotation-driven wiring from this bundle.