injectable | Opinionated and declarative Dependency Injection library | Dependency Injection library

Assign function for add_LicenceComponent of sharedService instead returning void.

Another thing is your getting TypeError because of service not initialised while trying to access it in constructor. Move it to ngOnInit() and do check do whether you added them in providers

You need to do some modifications in your component code like below,

Your @Get(':username') route handler defines that it should have a username parameter passed to it, but doesn't tell Nest how to pass it. You can do one of two things here:

1. use @Param('username') to pull the username directly from req.params['username']. Quick and easy

2. use @Param() { username } to deconstruct req.params to pull out just username (it should be the only value anyways). The benefit of this approach is being able to use the ValidationPipe with a DTO class to represent the req.params object. With the second approach, your @Get(':username') method would look like this:

Based on NestJS Websocket documentation, the NestJS socketIO server is still in v2.

@nestjs/platform-socket.io currently depends on socket.io v2.3 and socket.io v3.0 client and server are not backward compatible. However, you can still implement a custom adapter to use socket.io v3.0. Please refer to this issue for further information.

If you check the version compatibility, you will see that socketIO server v2 is not compatible with socketIO client v4.

The easiest solution would be to use socket.io-client v2.3.0 in your package.json of frontend.

Or, if you like to explore: socketIO server v3 is compatible with socketIO client v4. So I believe you can take a look into this issue (as mentioned in NestJS docs) and try to convert your NestJS socketIO server to support socketIO client v3. Hopefully, that would also support socketIO client v4 as well. (I didn't test this though!)

Hope this helps you. Cheers 🍻 !!!

There's no TypeOrmModule.forFeature([CashIn]) in your AppModule where you declare the CashInServce to be used. This is important because it tells Nest to create a provider to be used from the TypeOrmModule.

you should remove AuthService from LoginModule, because it creates another copy of this service in that module injector, and, because of that the other instance doesn't get the login state

Instead of passing the idKey as a constructor parameter, I would suggest reflecting it as metadata of the class. This way, you could do something like

Lifecycle hooks like ngOnInit work with Directives and Components. They do not work with other types, like a service in your case.

You are getting null value because verifydocumentMessage is declared as null and your ngOnInit is not called.

So, simply move ngOnInit logic to the constructor it will work fine.

You can try this:

I suggest adding the entities path oin your config so it can find files :