You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This project is not actively maintained anymore, but neither is "angular/di" according to issue 108. In that issue, injection-js is referred, but that is more opinionated (Decorators, di.Class, ...). In the mean time @nikku continued developing node-di on his fork: https://github.com/nikku/didi. This entire situation is kind of a mess to be honest.
Is it an idea to merge these 2 projects (node-di and didi) back together and make nikku the maintainer? That way there will be 2 DI frameworks, one unopinionated "node-di" (or "didi") and one based on Angular's reflective dependency injection mechanism.
It will be much clearer for any layman trying to choose the correct DI framework for his use case.
The text was updated successfully, but these errors were encountered:
This project is not actively maintained anymore, but neither is "angular/di" according to issue 108. In that issue, injection-js is referred, but that is more opinionated (Decorators,
di.Class
, ...). In the mean time @nikku continued developing node-di on his fork: https://github.com/nikku/didi. This entire situation is kind of a mess to be honest.Is it an idea to merge these 2 projects (node-di and didi) back together and make nikku the maintainer? That way there will be 2 DI frameworks, one unopinionated "node-di" (or "didi") and one based on Angular's reflective dependency injection mechanism.
It will be much clearer for any layman trying to choose the correct DI framework for his use case.
The text was updated successfully, but these errors were encountered: