@ogma/[email protected]

Patch Changes

• e7619e6: Trying a second publish to publish the js not ts

@ogma/[email protected]

Patch Changes

• bc6cdc8: Fix a bad publish from an incorrect workspace file

@ogma/[email protected]

Minor Changes

• 81b3501: Allow the CLI to accept process.stdin so it can be piped to.

  Now, if you want to have json: true always set in your Ogma config, but you still want to get the pretty dev logs, you can use something to the extent of pnpm start:dev | ogma and ogma will pretty print each line as it comes in.

@ogma/[email protected]

Patch Changes

• b730b78: resolve bad deployment of socket.io package

@ogma/[email protected]

Patch Changes

• 8973523: Fix the peer dependencies for socket.io and @nestjs/plaltform-socket.io

@ogma/[email protected]

Major Changes

• 5e51fdc: Update package versions to work with Nest v8

  Breaking Changes

  For @ogma/nestjs-module and all of the @ogma/platform-* packages, Nest v8 is the supported package version. Nest v7 may still continue to work, but has no guarantees. Also, RxJS is upgraded to v7 to stay inline with Nest's expectations.

  Why the change was made

  To stay current with Nest.

  How to upgrade

  Upgrade with Nest v8. There shouldn't be any breaking underlying changes, but you can never be too careful with coded upgrades.

@ogma/[email protected]

Major Changes

• 5e51fdc: Update package versions to work with Nest v8

  Breaking Changes

  For @ogma/nestjs-module and all of the @ogma/platform-* packages, Nest v8 is the supported package version. Nest v7 may still continue to work, but has no guarantees. Also, RxJS is upgraded to v7 to stay inline with Nest's expectations.

  Why the change was made

  To stay current with Nest.

  How to upgrade

  Upgrade with Nest v8. There shouldn't be any breaking underlying changes, but you can never be too careful with coded upgrades.

@ogma/[email protected]

Major Changes

• 5e51fdc: Update package versions to work with Nest v8

  Breaking Changes

  For @ogma/nestjs-module and all of the @ogma/platform-* packages, Nest v8 is the supported package version. Nest v7 may still continue to work, but has no guarantees. Also, RxJS is upgraded to v7 to stay inline with Nest's expectations.

  Why the change was made

  To stay current with Nest.

  How to upgrade

  Upgrade with Nest v8. There shouldn't be any breaking underlying changes, but you can never be too careful with coded upgrades.

Patch Changes

• Updated dependencies [5e51fdc]
  • @ogma/[email protected]

@ogma/[email protected]

Major Changes

• 5e51fdc: Update package versions to work with Nest v8

  Breaking Changes

  For @ogma/nestjs-module and all of the @ogma/platform-* packages, Nest v8 is the supported package version. Nest v7 may still continue to work, but has no guarantees. Also, RxJS is upgraded to v7 to stay inline with Nest's expectations.

  Why the change was made

  To stay current with Nest.

  How to upgrade

  Upgrade with Nest v8. There shouldn't be any breaking underlying changes, but you can never be too careful with coded upgrades.

@ogma/[email protected]

Major Changes

• 5e51fdc: Update package versions to work with Nest v8

  Breaking Changes

  For @ogma/nestjs-module and all of the @ogma/platform-* packages, Nest v8 is the supported package version. Nest v7 may still continue to work, but has no guarantees. Also, RxJS is upgraded to v7 to stay inline with Nest's expectations.

  Why the change was made

  To stay current with Nest.

  How to upgrade

  Upgrade with Nest v8. There shouldn't be any breaking underlying changes, but you can never be too careful with coded upgrades.