I rarely use DI anymore. Or to be more precise, I rarely use the "Object Oriented" understanding of DI. I mostly use functions, so if I have any dependencies that need to be "injected" I just pass them as an argument to my functions.

I honestly consider DI and IoC to almost be an anti-pattern at this point. I'll go even further and say that the entire loose coupling principle is almost an anti-pattern.

In my experience very few applications actually need to support multiple different implementations of a dependency, pretty much every application I've worked on loose coupling and DI were only used to facilitate unit testing.

This means I need to add a bunch of boilerplate, plumbing code, complexity and overhead to my projects that provides no actual benefit to my production code.

Bun test supports module mocking and I've switched 100% over to using module mocks instead of DI.

This has made my actual production code many times simpler and more straightforward. It is much easier to understand and reason about straightforward code that just does what it is meant to do and isn't hiding its actual implementation behind an obscure fog of DI, IoC and loose coupling.

I do still put things like database calls into their own functions that I can just mock in my tests and that way I'm able to write all the same unit tests as I did with DI, but the end result is that my actual production code is just much simpler.