service-binding

Use the service container's bind() method in a service provider's register() method, passing the interface and implementation class names. The Repository With Service package also binds interfaces automatically when implementations follow the RepositoryImplement naming convention.

Create a Mockery mock of the repository interface, define expected method calls with shouldReceive, then bind it to the container using $this->app->bind() or $this->instance(). Services resolved afterward will receive the mock instead of the real implementation.

Resolution failures usually come from unpublished config, mismatched naming conventions, or wrong namespaces. Verify the interface and implementation follow the configured suffixes, confirm files exist in the expected directories, and run php artisan config:clear.

Yes, use conditional binding by checking $this->app->environment() inside the register() method and binding different implementations per condition. You can also use contextual binding with when()->needs()->give() to vary implementations by consuming class.

bind() creates a new instance on every resolution, while singleton() registers the binding so the same instance is returned each time. Use singleton for stateless services where shared state is safe and desired.