iti VS typedi

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

In this tutorial, we're building a simple application which uses Cerbos inside of a GraphQL server. The server is written in typescript and uses type-graphql to create the schema and resolvers, and TypeDI to handle dependency injection.

typedi

If you don’t want to tie yourself to a full web framework like Nest, there are a few DI-only frameworks that work with decorators, like TypeDI, TSyringe, or Typed Inject.

For existing projects, or if you don't want the weight of an opinionated framework like Nest, libraries like TypeDI and TSyringe can help.

The TypeDI project aims for simplicity by leveraging decorators and decorator metadata. It supports dependency scoping with singletons and transient objects and allows for multiple DI containers to exist. You have two options for working with TypeDI:

There are a number of Javascript dependency injection container libraries out there. Some of my personal favourites are TypeDI and InversifyJS. Here is an example demonstrating basic usage of Typedi with JavaScript.

typedi TypeDI is a powerful dependency injection package that has many features. One of this features is having Singleton Services which is how we use it in our case.