docs.nestjs.com | The official documentation https : //docs.nestjs.com 📕 | Runtime Evironment library

I have this DTO class defined.

I'm trying here to do end to end testing with Jest on a NestJS/GraphQL app and Prisma as my ORM.

What happens here is Prisma is opening too many connections with Postgres, I've tried to fix this problem by using prisma.$disconnect() after each test but it doesn't seem to work...

This is what I've tried so far.

I'm trying to upgrade our NestJS GraphQL subscriptions server to utilize graphql-ws rather than the current subscriptions-transport-ws (as suggested by the NestJS documentation). I upgraded the NestJS version to

I am using nest.js, prisma, and graphql.
When I run the npm run start:dev command, I get an error.
If anyone knows how to solve this, please let me know.

ERROR [GraphQLModule] Missing "driver" option. In the latest version of "@nestjs/graphql" package (v10) a new required configuration property called "driver" has been introduced. Check out the official documentation for more details on how to migrate (https://docs.nestjs.com/graphql/migration-guide). Example:

GraphQLModule.forRoot({ driver: ApolloDriver, })

• How does the framework manage the lifetime of DynamicModules?

The NestJs documentation on Modules states that:

In Nest, modules are singletons by default, and thus you can share the same instance of any provider between multiple modules effortlessly.

• How can you share multiple dynamic module instances between modules?

The NestJs documentation on DynamicModules states that:

In fact, what our register() method will return is a DynamicModule. A dynamic module is nothing more than a module created at run-time, with the same exact properties as a static module, plus one additional property called module.

• How can you manage/change the scope of DynamicModules? For example, changing them from behaving transitively to as a singleton. Defining their injection token, retrieving them on demand, etc.

NestJS URI Versioning for HTTP REST applications can be easily enabled when following the docs here.

The docs do however not explain how to make URI versioning optional.

Example:

/api/v1/users

/api/v2/users

/api/users -> should be mapped to v1 to allow existing webhooks to keep working

Question:

How can we make the URI versioning optional in a NestJS REST application so that old versions (without any api version) keep working ?

I am implementing NestJS worker, queues, using Bull.

According to the documentation, both the worker and the server (will) run in a same "process", but I want to run the worker in a separate process, so as to not block the main event loop.

I think it's called "running a task in a separate binary" or something else.

Anyway, I tried googling it, went through the documentation of NestJS, but couldn't find something similar.

++ In other words:

I have a main project (my current), and I want to create the worker in a separate process (standalone application) and want to connect both my current main project and worker. And I can't really find it in the documentation.

In which module should I instantiate my Bull's instance? I am assuming I'll keep my producer in my main module and consumer in my worker module.

How can I do so?

Please note, by "separate process", I do not mean running a specific task in a separate process, as defined in Bull's documentation. I want to deploy the whole worker module in a separate process or whatever the term should be used.

++ [Extra, if possible]

Before running my server and worker, I also want to check whether my worker (bull instance) is successfully connected to my Redis server. I couldn't find anything on the Bull's documentation... do you think there is a good workaround for that?

Nestjs suggests to use the HttpModule, imported from @nestjs/axios to perform requests to external APIs. I understand that the HttpService transforms the responses into Observables.

Request data from an external API and use the data inside the application.

I fail to understand how to actually retrieve the data from the request. I read in some other answers, that if you return the observable from a Controller, Nestjs will automatically handle it for you and return the data to the client. That's great, however, I am not using it inside a Controller. I need the data to be available inside the application.

I have a service:

I am trying to make a POST request using @nestjs/axios and return the response.

This is my code: