The solution is to not use OO. JavaScript is not that good at it anyways.
Unfortunately legions of Javascript fanboys have recently noticed that they don't have the keyword 'class' in the language, but they do have functions and have decided this means that it's a functional programming language, and they knew better than everyone all along.
They'll then follow it up with some perfectly nice procedural code and tell themselves it's functional with a nice little pat on the back.
func: print "Hello World"
and be done with it. But when you grow, you realize that you need it to be able to print hello world in many languages so you add I18N
func: unicodePrint(geti18N(HELLO_WORLD))
getI18n(I18N_KEY): curlang.get(I18N_KEY)
1091_en: "Hello World
and then someone accidentally broke something so you want to be able to unit test it.
func(printer=stdoutprinter): printer.unicodePrint(geti18N(HELLO_WORLD))
getI18n(I18N_KEY): curlangmap.get(I18N_KEY)
1091_en: "Hello World
interface printer ...
singleton stdoutprinter ...
Ideally you'd want a framework that caters to all of these stages
In JS, one big problems is that you want your code to live in different files, and to do this, you either create your own ghetto object namespaces that hold your classes, or use requirejs.
In the case of Angular, they decided to handle this for you, so they provided IoC/DI as a means to accomplish this. They are merely doing this to make up for things that are missing in javascript as a language.
In their defense, it actually works kind of nice compared to the other two approaches imho.