Dependency inversion - YES! classes should be honest and declare in the constructor what they need to function correctly.
Dependency injection - If the app is large enough that it make sense to use a DI container, sure. Almost all of what I write these days is either Angular or ASP.NET Core web applications, so Dependency injection is pretty much a guarantee.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.