CLI command doesn't work with a request scoped dependency about nestjs-console HOT 4 CLOSED

We've came up with a solution. We created a new class decorator, which overrides the default @Injectable() decorator.

import { Injectable, InjectableOptions, Scope } from '@nestjs/common';
import { basename } from 'path';

export function InjectableCliAware(options?: InjectableOptions): ClassDecorator {
  if (basename(process.argv[1]) === 'console.js' && options?.scope === Scope.REQUEST) {
    options.scope = Scope.DEFAULT;
  }
  return Injectable(options);
}

So I think, we can close this issue?! :)

from nestjs-console.

You can't inject scoped service in a non scoped service.
@Injectable({ scope: Scope.REQUEST }) means your service only exists when a request is created.

Scoped thing does not make sense in a headless app.

See https://docs.nestjs.com/fundamentals/injection-scopes#scope-hierarchy

Scope bubbles up the injection chain. A controller that depends on a request-scoped provider will, itself, be request-scoped.

from nestjs-console.

Hello @Rmannn,

thank you for your quick reply. :)

Sooo, the only solution for us would be to duplicate the request scoped service to be not request scoped (we can not simply drop the request scoping, as this service holds a request based cache (for the GraphQL- and REST-contexts).

As already said, we are aware that this kind of thing doesn't make much sense for a headless app, but we wanted to reuse the service to reduce code duplication.

Do you have another solution in mind?

from nestjs-console.

Nice solution!

from nestjs-console.