Weave Code
Autoconfigure Bundle Laravel Package
rich-id/autoconfigure-bundle
Rich ID Autoconfigure Bundle simplifies Symfony service configuration by applying convention-based defaults, reducing boilerplate and keeping dependency injection setup clean and maintainable. Suitable for PHP projects that want faster autoconfiguration with minimal manual wiring.
Create easy autoconfigurations with annotations to add tag to a service, inject service and arguments, or decorate another service
Frequently asked questions about Autoconfigure Bundle
- What is rich-id/autoconfigure-bundle used for?
- It is a Composer-installable bundle that registers and wires services through convention-based configuration instead of hand-written bootstrap code. It provides zero-boilerplate setup for supported services and extensions, discovers classes and configuration by convention, and applies sensible defaults that remain straightforward to override. The goal is predictable, maintainable dependency injection setup for PHP applications.
- Does rich-id/autoconfigure-bundle work with Laravel?
- Not out of the box. It is a Symfony bundle layered over Symfony's dependency injection container and compiler passes, while Laravel resolves services through Illuminate\Container. The tag-injection and attribute-driven method-call patterns it offers are conceptually similar to Laravel's tagged() and contextual binding, but adopting it in a Laravel application would mean maintaining a second, parallel DI idiom, so treat it as a design reference or use Laravel-native bindings instead.
- How do I install rich-id/autoconfigure-bundle?
- Install it with Composer using composer require rich-id/autoconfigure-bundle, then register the bundle in your bundle configuration such as config/bundles.php. Check the package composer.json for minimum PHP and framework constraints before installing. Because it is lightweight and Composer-ready, it should not pull in heavy runtime dependencies beyond the framework itself.
- Which PHP and Symfony versions does the bundle support?
- The summarized release notes do not state an explicit version matrix, so verify the constraints in composer.json and in the CI configuration before adoption. If the method-annotation layer relies on PHP 8 attributes rather than docblock parsing, PHP 8.0 or later is required. Symfony container internals shift between major versions, so match the bundle to the Symfony version you actually run in production.
- How does tag injection interact with Laravel's tagged() and contextual binding?
- In Symfony, tags feed compiler passes and tagged service locators at container build time, whereas Laravel's tagged() and when() resolve collections and contexts at runtime. If you port tag injection into Laravel, it can shadow native binding ownership and make it hard to trace where a concrete implementation was resolved from. Avoid overlapping the two mechanisms on the same services and document the resolution order.
- Are tag injection and method annotations opt-in, and is the upgrade non-breaking?
- The features appear to be additive configuration primitives: definitions that do not use tags or method annotations should resolve exactly as before, which suggests a non-breaking minor release. However, the release notes summarized here do not state backward compatibility explicitly. Confirm with the changelog diff and check that the package follows semantic versioning before upgrading inside a shared codebase.
- Will autoconfigured services survive config caching in production?
- This is the first thing to verify. If definitions are compiled at container build time, they must be honored after php artisan config:cache and route:cache in Laravel, or after cache warmup in Symfony, otherwise production behavior will diverge from local. Run a cold-start test in staging and compare container build time and resolved services before rolling out.
- How should I test the container after enabling autoconfiguration?
- Add a smoke test that boots the container and resolves the key services, plus a CI step that compiles the container and asserts the expected tagged services are present. Run your static analysis and IDE tooling over the annotated classes, and if the annotation syntax is bespoke, accept reduced Psalm or PHPStan coverage there or exclude those files. Instrument container build time before and after in a pilot module.
- What are the alternatives to this bundle for service autoconfiguration?
- In Symfony, native autowire and autoconfigure, resource-based service discovery, _instanceof rules and service tags cover most of the same ground without an extra dependency. In Laravel, AppServiceProvider bindings, contextual attributes and tagged() collections are the native equivalents. Choose based on which DI idiom your team already documents and enforces.
- Is the package actively maintained and safe to adopt incrementally?
- Check the GitHub repository for release cadence, issue-response history, semantic versioning discipline and a CI-verified version matrix before committing. Adopt it in one bounded module rather than a codebase-wide retrofit, leaving existing providers untouched. Removal is low-risk: delete that module's definitions and drop the Composer dependency, with no data or schema implications.
Weaver
How can I help you explore Laravel packages today?