tsyringe VS tslib

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.

It's appropriate for software designed for use cases where an attribution requirement would be inconvenient or otherwise undesirable. For example, https://github.com/microsoft/tslib uses it, because that library is automatically included in any TypeScript program that uses downleveling, so if it had an attribution requirement then that requirement would apply to every program written in TypeScript, which nobody wants. (GCC and LLVM do something similar with their special runtime-library exceptions to the GPL and Apache License, respectively, but tslib lives in a separate repository from the rest of TypeScript and so could easily just get a separate license.)

Looking at some popular JavaScript projects on GitHub, I noted that react, moment, and express all use single quotes for strings. However, another popular project, tslib, uses double quotes 🙄. So, while it would seem that single quotes is more common, this metric is not entirely conclusive.

Things get a little interesting if you're using CommonJS interoperability, in which case our second import becomes something like const view2 = __importDefault(require("./view2")).default. This helper function checks to see if the imported file is an ES module and effectively namespaces the module under the default property if not. You can see TypeScript's implementation of this here.

You may just copy them from tslib. It's 0BSD-licensed which doesn't even require attribution; but having the link somewhere in your comments is at least polite 🙂