Thoughs about angular/di.js@2.0 and DRY

main.js

var di = require('di');
/* Here comes the interesting part:
   We pass some kind of module loader into di (require for node or RequireJS apps)
   We'd have to add some configuration for async/promise support
   
   The string-tokens we use in our app will than be loaded/required and di will then use the Object/Class/whatever
   as internal Token.
 */
di.moduleLoader(require);
var injector = new di.Injector([]);

/* The injector requires MyClass.js, sees that it needs MyOtherClass.js and fs.readFile from node, requires ans resolves them
and injects them into the MyClass constructor */
myClass = injector.get('./MyClass').doThings();

MyClass.js

/**
 * Just a simple example Class
 * Main point here is: This is completely independent from di implementations
 * We could as well require this file and instantiate the Class on our own
 */
function MyClass(myOtherClass, readFile) {
  this.myOtherClass = myOtherClass;
  this.readFile = readFile;
  this.doThings = function() {};
}
/* yes, we have again strings as tokens, but in most cases (exept, we define all modules in the same scope)
   we would have had to write these strings somewhere else */
MyClass.inject = ['./MyOtherClass', 'fs.readFile']

module.exports = MyClass

MyOtherClass.js

module.exports = function MyOtherClass() {}