diddly VS InversifyJS

These past days I've been working on a super strongly typed IoC container library that works on Deno. It's based on work from u/Tomus (his Diddly library: https://github.com/tom-sherman/diddly).

I've toyed with a similar pattern, albeit a purely functional one https://github.com/tom-sherman/diddly

Take a class for which we are tasked to write a unit test. This class may have a dozen methods and a dozen more attributes. In my environment we were already using inversify to dependency inject into this class, and using container snapshot and restore as setup and teardown operators, in our jest test file. But it began getting out of control even after refactoring into test cases and test runners.

Inversify (https://inversify.io/) for IoC.

Alguns frameworks trabalham desta forma por padrão, como é o caso do Angular, quando este não é o padrão do framework que utilizamos podemos usar alguma biblioteca, como a Inversify ou tsyringe da Microsoft.

Using decorators required setting an --experimentalDecorators experimental compiler flag. Several popular TypeScript libraries, such as type-graphql and inversify, rely on this implementation.

inversify

It blows 🤯 my mind to think that my #opensource project InversifyJS has reached over 100 MILLION DOWNLOADS on npm. InversifyJS is a lightweight (<50KB) but powerful Inversion Of Control (IoC) container for #JavaScript applications powered by #TypeScript. It is used to implement Dependency Injection (DI) in thousands of applications, including high-profile products like Microsoft Sway and over forty thousand open source repositories on #GitHub and over two thousand open source packages on #npm.

we use https://inversify.io/ in production, it works great.