typedi | Simple yet powerful dependency injection tool | Dependency Injection library

I got curious, and found the answer in the TypeORM documentation here:

TypeScript configuration

Also, make sure you are using TypeScript version 4.5 or higher, and you have enabled the following settings in tsconfig.json:

If you want a value to be null, you should put it on both.

{ nullable: true } in typeorm (@Entity) means the database is permitted to store null values. Otherwise, you can't even save an entity without defining that column.

{ nullable: true} in type-graphql (@Field) means that the schema generated by TypeGraphQL will permit that field to be null. Otherwise, when querying, you would expect to potentially get an error of Cannot return null for non-nullable field EntityName.fieldName.

To clarify, the GraphQL schema might look like:

I updatedt the getRouter method to fix the issue:

First of all, try to put your initializeRepositories call right after the reflect-metadata call, to test if the execution order will impact. You don't need to call inside the database connection file.

From what I saw at the old docs, to use Container.set to set all of your repos, you need to provide an array containing objects with id for them.

Container.set([{ id: 'userRepository', value: new UserRepository() }])

If you just need to set a single repository:

Container.set('userRepository', new UserRepository())

In both cases above, you use like: Container.get('userRepository');

If you want to keep the reference as repositories your initializeRepositories method is ok, but the usage must be like:

You can make sure that you have to set a static value with decorators. The approach would look like this:

Maybe it's the same problem as described here

Try switching to,

It really depends on your scenario. If AClientMethodsImplementation is meant to be stateless (it will not hold instance related data between method calls) you should declare all of its members static:

Node v14 introduced a breaking change to the fs.watch() API, specifically that the recursive option (which has never been supported on Linux) now raises the ERR_FEATURE_UNAVAILABLE_ON_PLATFORM error if used on Linux.

A bug report and fix have been submitted to filewatcher: https://github.com/fgnass/filewatcher/pull/6

Until that fix is merged and a new version released, you'll need to stick to NodeJS < v14, or override the filewatcher package installed locally to include that patch.