How us use a command inside of nest scheduler?

[9x3l6]

How to inject command into a service or processor or scheduler to run command from there?

[jmcdo29]

Why would you need to run a CLI command from the processor/scheduler instead of using the service directly?

[9x3l6]

So to not write duplicate code, I'd like to run the command from a scheduler in a cron while my nest application is running, and I want to be able to run the commands manually when I need

[jmcdo29]

Well, to run a command from within a node application you use the child_process package from Node and spawn or exec a new shell to run the command.

[9x3l6]

Okay, that works. I just thought maybe there would be a way to @InjectCommand(BasicCommand) or something like that. It would probably consume more memory to run than a child_process, am I right?

[jmcdo29]

In the end, commands are just @Injectable() classes (well @Command(), but that just sets metadata that nest-commander makes use of to parse options) so you could techincally inject the command and call .run yourself, but you won't get any of the @Option() methods to parse the options for you.

[9x3l6]

Can you show me code example say with BasicCommand example that you have? Cuz I tried before asking and it get errors

[jmcdo29]

So long as the BasicCommand is in the providers array, or it is in the exports of a module that is in the imports there shouldn't be any problems.

@Module({
  imports: [BasicModule], // has `BasicCommand` in the `exports` and `providers` arrays
  providers: [SomeProcessor],
})
export class SomeModule {}

@Processor('some event')
export class SomeProcessor {
  constructor(private readonly basicCommand: BasicCommand) {}

  @Process()
  async processEvent() {
    await this.basicCommand.run(inputsStringArray, optionsObject);
  }
}

In theory, this would do fine

[9x3l6]

That works great, thanks for your help