nestjs

I'm trying to setup a MQTT Microservice using NestJS according to the docs . I've started a working Mosquitto Broker using Docker and verified it's operability using various MQTT clients. Now, when I start the NestJS service it seems to be connecting correctly (mqqt.fx shows new client), yet I am unable to receive any messages in my controllers. This is my bootstrapping, just like in the docs: main.ts async function bootstrap() { const app = await NestFactory.createMicroservice(AppModule, { transport: Transport.MQTT, options: { host: 'localhost', port: 1883, protocol: 'tcp' } }); app.listen(()

I am trying to make use of the AuthGuard decorator, and the passport JWT strategy, following the documentation . Everything in the documentation works great. But I now want to protect a route with a scope contained in the JWT. So here is a basic jwt payload generated by my application: { "user": { "id": "20189c4f-1183-4216-8b48-333ddb825de8", "username": "user.test@gmail.com" }, "scope": [ "manage_server" ], "iat": 1534766258, "exp": 1534771258, "iss": "15f2463d-8810-44f9-a908-801872ded159", "sub": "20189c4f-1183-4216-8b48-333ddb825de8", "jti": "078047bc-fc1f-4c35-8abe-72834f7bcc44" } Here is

I want to use an in-memory Mongo instance to mock data for testing purposes in my NestJS application. I have a database provider which connects to my production db using mongoose, which is part of my database module, which in turn gets imported into other modules. I am trying to override the database provider within my Jest tests so I can use the in-memory Mongo instance. This is the database module: import { Module } from '@nestjs/common'; import { databaseProviders } from './database.providers'; @Module({ providers: [...databaseProviders], exports: [...databaseProviders], }) export class

While using NestJS to create API's I was wondering which is the best way to handle errors/exception. I have found two different approaches : Have individual services and validation pipes throw new Error() , have the controller catch them and than throw the appropriate kind of HttpException ( BadRequestException , ForbiddenException etc..) Have the controller simply call the service/validation pipe method responsible for handling that part of business logic, and throw the appropriate HttpException . There are pros and cons to both approeaches: This seems the right way, however, the service can

I have implemented a generic class as below which might be causing the problem, import { Logger } from '@nestjs/common'; import { PaginationOptionsInterface, Pagination } from './paginate'; import { Repository } from 'typeorm'; export class EntityService<T> { private repository: Repository<T>; constructor(repository) { this.repository = repository; } async getEntityWithPagination( options: PaginationOptionsInterface, ): Promise<Pagination<T>> { const [results, total] = await this.repository.findAndCount({ take: options.limit, skip: (options.page - 1) * options.limit, }); return new Pagination

In the REST API below, what is the type of file object that is received. @Post('/:folderId/documents/:fileName') @UseInterceptors(FileInterceptor('file')) @ApiConsumes('multipart/form-data') @ApiImplicitParam({ name: 'folderId', description: ' Folder Id' }) @ApiImplicitParam({ name: 'fileName', description: ' File Name' }) @ApiImplicitFile({ name: 'file', required: true, description: 'PDF File' }) async uploadFile(@UploadedFile() file, @Param() folderId, @Param() fileName) { /** * I need to know the type of file object (first argument) of uploadFile */ this.folderService.uploadFile(file,