nest-commander-testing/CHANGELOG.md

A testing utility for nest-commander. It builds on top of ideas from @nestjs/testing and is not tied to any test framework directly.

# nest-commander-testing

## 3.5.0

### Minor Changes

- ca7ee4b: Bump @golevelup/nestjs-discovery from v4 to v5

## 3.4.0

### Minor Changes

- ce3d4f4: Support NestJS v11

## 3.3.0

### Minor Changes

- 519018e: Add ability to set outputConfiguration.

  Now CommandFactory.run(), CommandFactory.runWithoutClosing() and
  CommandFactory.createWithoutRunning() accept the option `outputConfiguration`.

## 3.2.0

### Minor Changes

- 1fa92a0: Support NestJS v10

## 3.1.0

### Minor Changes

- c75ca13: Add runWithoutClosing for testing

## 3.0.1

### Patch Changes

- 23b2f48: Add 3.0.0 to peer deps

## 3.0.0

### Major Changes

- d6ebe0e: Migrate `CommandRunner` from interface to abstract class and add
  `.command`

  This change was made so that devs could access `this.command` inside the
  `CommandRunner` instance and have access to the base command object from
  commander. This allows for access to the `help` commands in a programatic
  fashion.

  To update to this version, any `implements CommandRunner` should be changed to
  `extends CommandRunner`. If there is a `constructor` to the `CommandRunner`
  then it should also use `super()`.

### Minor Changes

- 3d2aa9e: Update NestJS package to version 9

## 2.0.1

### Patch Changes

- 3831e52: Adds a new `@Help()` decorator for custom commander help output

  `nest-commander-testing` now also uses a `hex` instead of `utf-8` encoding
  when creating a random js file name during the `CommandTestFactory` command.
  This is to help create more predictable output names.

## 2.0.0

### Major Changes

- ee001cc: Upgrade all Nest dependencies to version 8

  WHAT: Upgrade `@nestjs/` dependencies to v8 and RxJS to v7 WHY: To support the
  latest version of Nest HOW: upgrading to Nest v8 should be all that's
  necessary (along with rxjs to v7)

## 1.2.0

### Minor Changes

- f3f687b: Allow for commands to be run indefinitely

  There is a new `runWithoutClosing` method in the `CommandFactory` class. This
  command allows for not having the created Nest Application get closed
  immediately, which should allow for the use of indefinitely runnable commands.