Nest cant resolve dependencies on latest NestJS about bull HOT 9 CLOSED

Yes, I think so. With #116 it will be a better solution.

Leaving a sample of shared module for anyone who is interested:

const QueueModule = BullModule.forRoot({ // BullModule.register
  name: 'test',
});

@Module({
  imports: [QueueModule],
  exports: [QueueModule],
})
export class SharedModule {}

from bull.

Hi @maksimkurb and thanks for reporting.
Was your sample working before NestJS 6.3.1?

from bull.

Sorry, did an example in a hurry, so I made some mistakes. Now I updated it and this is correct, that it is not working on NestJS 6.3.1, but working fine on NestJS 6.3.0

from bull.

@fwoelffel, I got it! We should add @Global() decorator to BullModule so we can use queue in other modules. Another option is to create method BullModule.forFeature() like in TypeORM module, but this will be a breaking change.
I will create a pull request in a couple of minutes

from bull.

I think having a SharedModule that exports your queue, and that is imported in whichever modules where you need the queue to be injected, could solve your issue.
Would you try that? I'd prefer not to increase the code complexity as long as this can be avoided.

from bull.

I really don't like the Global solution 😉

from bull.

SharedModule is also the solution, but then forRoot method name is confusing. Better to be called register like in HttpModule

from bull.

I understand that. I think the real issue here is the lack of documentation/examples.

Anyway, should we close this issue?

from bull.

I need create sessions for handle queues of inline clients, when creating a new session, I need to create a new queue with session name (dynamic) , but in nestjs docs you always know the queue name for registering and later inject it . How i can manage the dynamic creation of bull queues in nestjs?

from bull.