nestjs | badass modules and utilities to help you level | Web Framework library

After hours of searching, the solution is to add

what worked for me was, everything in backticks for eg : `t1.Id = t2.column_name->'$.Id'

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:

For something like this, you'll either need to make use of something like Nest's undocumented DiscoveryService or a package like @golevelup/nestjs-discovery which is a friendly wrapper around Nest's package. You can then make use of methods like this.discoveryService.methodsAndControllerMethodsWithMetaAtKey to get the classes and methods that have that metadata, then you can use the reflector class on each method to get the metadata value.

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.

This log was recently added in the Cloud Run data path to provide more context for debugging CloudSQL connectivity issues. However, the original logic was overly aggressive, emitting this message even for properly working CloudSQL connections. Your application is working correctly and should not receive this warning.

Thank you for reporting this issue. The fix is ready and should roll out soon. You should not see this message anymore after the fix is out.

You can try setting it manually while bootstrapping.

Try to use: app.disable('x-powered-by') - so all lower-case and it should work!