iti VS InversifyJS

I didn’t want to adopt a framework for a bigger one, so I’ve built a manual DI helper.

It is for typescript. It is really helpful for me.

https://itijs.org

If you are interested, I wrote an obscure DI helper library to help mi with ts/react/nest apps. Most examples use classes, but it perfectly works with pure functions. Nothing groundbreaking, just helps me ship apps with lazy async data pipelines faster https://github.com/molszanski/iti

I've had success in adding an iti to an existing 50K app

Vorarbeiter Service Container is about 10 times lighter then InversifyJS. It has simpler API and works faster.

One of the most popular libraries in JavaScript for implementing the Inversion of Control (IoC) pattern is InversifyJS. It provides a robust and flexible framework for managing dependencies in a clean, modular way. However, InversifyJS has some drawbacks. One major limitation is the amount of boilerplate code required to set up and manage dependencies. Additionally, it often requires structuring your application in a specific way, which may not suit every project.

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