'library-like' module using its own Ember.Container instance?


#1

I’m working on a module that depends on Emberjs but doesn’t depend on the existence of an Ember.Application instance – at this point its a little bit speculative but in my mind I would like to be able to reuse some or all of this code in a non-browser environment (node) down the road.

Is there any reason not to create my own Ember.Container instance within my library for the purpose of having a flexible way to organize my library pieces internally?