nest-commander@3.9.0

Minor Changes

• 1fa92a0: Support NestJS v10

nest-commander-testing@3.2.0

Minor Changes

• 1fa92a0: Support NestJS v10

nest-commander@3.8.0

Minor Changes

• 6cc1112: Add ability to pass NestApplicationContextOptions to CommandFactoryRunOptions.

  Now CommandFactory.createWithoutRunning() can accept more options, for example,
  bufferLogs to pre-save Nest startup logs.

nest-commander@3.7.1

Patch Changes

• 1ceab9d: Log error and stack wtih custom error message instead of just custom error
  message

nest-commander@3.7.0

Minor Changes

• 9a5f555: Add a new method to create an application but nott run it in case of needing to
  modify the logger or similar situations.

  Now the CommandFactory.createWithoutRunning() method can be used to create a
  Nest commander application without running the commandRunner.run(). To run the
  newly created application, CommandFactory.runApplicaiton(app) can be called. I
  may change this to be a simple app.run() in the future.

nest-commander@3.6.3

Patch Changes

• 84b5067: Adds support for positional options and passthrough options

nest-commander@3.6.2

Patch Changes

• 6fb3d91: Fix the Inquirer type to work above @types/inquirer@8.2.1

nest-commander@3.6.1

Patch Changes

• c35e8cc: Fixed issue with parsing serviceErrorHandler option to properly override default behaviour

nest-commander@3.6.0

Minor Changes

• 7f54ff8: Add serviceErrorHandler option

  This option allows for catching and handling errors at the Nest service execution level so that
  lifecycle hooks still properly work. By default it is set to
  (err: Error) => process.stderr.write(err.toString()).

• 09b6134: Add the ability to have a Root command

  With the @RootCommand() the -h flag can now output the options of the default command along
  with the names of the other commands.

nest-commander@3.5.0

Minor Changes

• d2e5fc8: Allow for use of request scoped providers through a new module decorator

  By making use of the @RequestModule() decorator for modules, as mock request object can be set as a singleton to help the use of REQUEST scoped providers in a singleton context. There's now also an error that is logged in the case of a property of undefined being called, as this is usually indicative of a REQUEST scoped provider being called from a SINGLETON context.