Weave Code
Service Annotation Bundle Laravel Package
terminal42/service-annotation-bundle
A Symfony bundle that lets you define and configure dependency-injection services using PHP annotations, reducing boilerplate YAML or XML. Annotate classes to register services, tags, and dependencies automatically.
At a glance
Frequently asked questions about Service Annotation Bundle
- Is terminal42/service-annotation-bundle a Laravel package?
- No. It is a Symfony bundle that provides annotation or attribute-driven service registration for Symfony's dependency-injection container. Laravel's container has no bundle or extension-point equivalent, so this is not a native Laravel package. In a Laravel estate it should only appear as a transitive dependency of an embedded Symfony kernel or a legacy Symfony/Contao module.
- Can I use terminal42/service-annotation-bundle directly in a Laravel application?
- Generally no. The package needs a Symfony kernel and Symfony DI container to be meaningful, and it does not use Laravel package discovery. It is only relevant if your Laravel app embeds a Symfony surface or pulls the bundle in transitively. Treat that as an exception rather than a pattern.
- How do I install terminal42/service-annotation-bundle?
- Install it with Composer using the package name terminal42/service-annotation-bundle, then register the bundle in a Symfony application kernel. Installation is Composer-level only and there is no Laravel package discovery. It is only worth installing where you already have a Symfony 6.4 or 7.x surface that uses annotation or attribute-based service configuration.
- Which Symfony versions does terminal42/service-annotation-bundle 1.1.6 support?
- Version 1.1.6 widens the Symfony constraint to allow Symfony 7 alongside existing Symfony 6.x support. The release is a patch-level compatibility relaxation with no API changes. Verify that your other pinned dependencies also accept Symfony 7, otherwise the widened constraint buys nothing.
- What PHP version is required for Symfony 7 support in this package?
- Symfony 7 itself requires PHP 8.2 or later, so resolving this package into a Symfony 7 application imposes that PHP floor. The 1.1.6 release widens the Symfony constraint but does not change the underlying PHP requirement of your stack. Check your application's PHP version before relying on Symfony 7 resolution.
- Does terminal42/service-annotation-bundle 1.1.6 introduce breaking changes?
- No. The 1.1.6 release contains a single change that widens the Symfony constraint to allow Symfony 7. There are no breaking changes, API changes, deprecations, or new features. It is safe to absorb, but note that the practical effect is that the package becomes newly installable in Symfony 7 contexts.
- How does terminal42/service-annotation-bundle compare with Laravel service providers or Symfony autoconfigure?
- Laravel service providers are the native way to register container bindings in Laravel, and Symfony autoconfigure plus attributes is the native modern approach in Symfony. This bundle is specifically for annotation or attribute-driven service registration against Symfony's DI container. It is not a replacement for Laravel service providers and should not be adopted as one.
- Is terminal42/service-annotation-bundle actively maintained?
- It is best treated as a maintenance-mode package. The context shows a single maintainer, low release velocity, and community-only support with no vendor SLA. Budget for it working without active roadmap investment, and price in a fork or vendor patch if it ever becomes load-bearing.
- What are the production risks of using terminal42/service-annotation-bundle?
- The most likely risk is dependency resolution rather than runtime behavior: future Symfony majors may again be excluded until a volunteer files a pull request. Maintainer abandonment is a standing risk for a single-maintainer package, and the 1.1.6 change means the bundle can surface in Symfony 7 contexts where it was not previously installable. Scaling impact is negligible because this is a container-compile-time concern, not a request-path concern.
- How do I check whether terminal42/service-annotation-bundle affects my Laravel dependency graph?
- Run composer why terminal42/service-annotation-bundle and composer depends terminal42/service-annotation-bundle to confirm reachability. If it is unreachable, no action is needed beyond tracking it. If it is reachable on Symfony 6.x, fold 1.1.6 into the next routine dependency refresh, and if it unblocks Symfony 7, sequence it after the Symfony 7 plan is approved and rerun the integration suite.
Weaver
How can I help you explore Laravel packages today?