tsyringe VS typed-inject

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.

We are writing a backend application that handles a data stream and provides REST and GraphQL endpoints to query and manage these data. We are using TypeScript with Express.js and TSyringe for our DI container.

This is exciting but also make be a bit nervous as my projects make extensive use of https://github.com/microsoft/tsyringe and the decorator changes are not going to play nice.

tsyringe

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.

In next post I will show you how to using with other DI package like awilix , tsyringe, etc...

It is written in Typescript, it is modeled similarly to the Microsoft tsyringe (which I was using previously).

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

I personally still always opt for that pattern to start with and refactoring to some sort of Reader monad as the application grows. Others may prefer instead to go the route of decorators and reflection with tsyringe.

typed-inject

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.

The Typed Inject project focuses on type safety and explicitness. It uses neither decorators nor decorator metadata, opting instead for manually declaring dependencies. It allows for multiple DI containers to exist, and dependencies are scoped either as singletons or as transient objects.