Weave Code
Di Laravel Package
slick/di
Slick\DI is a lightweight dependency injection container for PHP that wires services through autowiring, explicit bindings, and lazy resolution. It offers a small, PSR-11 friendly API for managing object lifecycles in Laravel, Slim, and standalone applications.
slick/di is a lightweight, PSR-11 compatible dependency injection container for PHP that resolves class dependencies automatically through autowiring. It keeps service configuration minimal, letting you bind interfaces to implementations, register shared instances, and lazily instantiate services only when needed.
Designed to integrate cleanly with Laravel and standalone PHP applications, it supports constructor injection, contextual bindings, and deferred resolution without heavy boilerplate.
- Autowiring for constructor-based dependency resolution
- Interface-to-implementation bindings and singletons
- PSR-11 compliant container interface
- Lazy service instantiation and deferred providers
- Seamless Laravel service provider integration
Frequently asked questions about Di
- Is slick/di compatible with Laravel?
- slick/di is not Laravel-native and has no Laravel service provider, facade, or configuration bridge in the provided context. It is a standalone PSR-11-style container from the Slick framework, so using it in Laravel requires an adapter layer and explicit lifecycle management. Laravel's built-in container already covers constructor injection, contextual binding, interfaces, and deferred providers. Treat slick/di as an isolated integration for a legacy or third-party subsystem, not a drop-in Laravel component.
- Can I replace Laravel's service container with slick/di?
- No, replacing Laravel's container is not recommended and would duplicate core framework behavior. Laravel expects its own container for service providers, facades, middleware, queued jobs, and framework resolution. A second container introduces unclear singleton scope and exception semantics. Keep Laravel as the application container and only wrap a specific consumer if a real requirement exists.
- How do I install slick/di with Composer?
- You can install it with Composer using the package name slick/di, but verify the available version constraints and PHP requirements before adding it to a Laravel project. There is no documented Laravel auto-discovery or service provider in the context, so installation alone does not integrate it with Laravel. Add it in a branch or spike first and confirm the license before production use.
- Does slick/di support PSR-11 dependency injection?
- The package is described as a standalone PSR-11-style dependency injection container, but the context does not confirm the exact PSR-11 version or exception behavior. You should verify Composer constraints and run contract tests for get, has, missing bindings, and thrown exceptions. If your integration depends on PSR-11 interoperability, test it against the target Laravel and PHP versions.
- How does autowiring work in slick/di?
- slick/di is intended to bind and resolve classes and autowire constructor dependencies with minimal boilerplate. The context does not document Laravel-style contextual binding, interface mapping, or deferred providers. In a Laravel integration, explicitly seed the Slick container with dependencies owned by Laravel rather than relying on hidden bidirectional resolution. Test constructor injection and missing-binding behavior before production.
- How do I manage shared instances or singletons in slick/di?
- The container supports shared instances, but the context does not define its exact singleton lifecycle or reset semantics. In Laravel, dual-container singleton state can drift, especially under Octane or long-running workers. Register one Slick container as a Laravel singleton only for an isolated subsystem and document when shared instances are created, reused, and reset. Add tests for repeated resolution and worker lifecycle behavior.
- How do I integrate slick/di into a Laravel service provider?
- There is no native Laravel bridge, so you would write an adapter service provider that creates a Slick container, seeds it with required Laravel-managed dependencies, and exposes only the minimal API needed by the legacy consumer. Avoid registering Slick as a general replacement for Laravel bindings or allowing bidirectional container resolution. Keep the adapter small, test missing bindings and circular dependencies, and include a fallback or kill switch.
- What license does slick/di use?
- The repository reports an unclear license with NOASSERTION, which means the actual license terms are not confirmed in the provided context. That creates legal and redistribution risk for commercial Laravel applications. Have legal review the package license and upstream ownership before adoption, and do not assume it is safe to ship without approval.
- Is slick/di safe and maintained for production Laravel apps?
- Adoption signals are effectively absent: the context reports 0 stars, 0 dependents, and no visible Laravel community integration. A 2024-08-15 release suggests some packaging activity, but it does not establish long-term support or security patching. For production, require internal ownership, contract tests, dependency version alignment, and a rollback plan. The technical risk is high relative to the value for a standard Laravel app.
- What are alternatives to slick/di for Laravel dependency injection?
- Laravel's built-in service container is the primary alternative and already supports constructor injection, interfaces, contextual binding, deferred providers, and PSR-11 interoperability. For standalone PHP projects, evaluate maintained PSR-11 containers with clear licenses and active dependents. Only consider slick/di when an existing Slick component or vendor package explicitly requires it and the integration can remain isolated.
Weaver
How can I help you explore Laravel packages today?