No access to global Container when used in node npm module about dependency-injection

[EisenbergEffect]

@weagle08 I'm skeptical that this is an issue inside of Aurelia. The makeGlobal API is pretty simple and straight forward in implementation. When I've seen things like this before, it's been due to different versions of modules being loaded. So, maybe the plugin has its own node_modules folder and is loading DI from there so that two instances are in memory with one globalized but the other not.

[weagle08]

I'll keep checking, but in the debugger there are no other globals that would override Container. Thanks for the feedback.

[weagle08]

Also, there is no other DI as I wrote all the code and am familiar w/ the libraries being used. If you want a reproduction project I can attach one if one of the Aurelia guys want to take a look.

[EisenbergEffect]

If you can attach a project with some basic instructions for me, that would greatly help.

[weagle08]

It appears you are right. When creating the bare minimum project to reproduce it runs fine so some other module is interfering. I'll start adding items back in slowly and keep an eye out for what breaks it.

Thanks,

Ben