Every package is released together, so they all move to 1.5.0. Install core, decorators and the adapter you actually use — swap mongoose for prisma or typeorm as needed.

$npm i @nest-extended/core@^1.5.0 @nest-extended/decorators@^1.5.0 @nest-extended/mongoose@^1.5.0

And the CLI, if you have it installed globally:

$npm i -g @nest-extended/cli@^1.5.0

1.5.0 is built against NestJS 12 and TypeScript 6. Applications still on NestJS 11 will usually run, but the published types target 12 — upgrade both together.

$npm i @nestjs/common@^12 @nestjs/core@^12 @nestjs/platform-express@^12
$npm i -D typescript@^6

Add the ORM-specific NestJS integration you use — @nestjs/mongoose@^12 or @nestjs/typeorm@^12.

Prisma 8 (“Prisma Next”) is a different product: prisma init --datasource-provider, prisma generate and prisma db push no longer exist, the ORM commands moved under prisma orm, and the client layout changed. Everything the generator emits targets Prisma 7.

$npm i @prisma/client@^7 @prisma/adapter-pg@^7
$npm i -D prisma@^7

Swap @prisma/adapter-pg for @prisma/adapter-mariadb (MySQL) or @prisma/adapter-better-sqlite3 (SQLite).

This is the change that turns service events on. Each NestService now has two families: _find / _get / _create / _patch / _remove stay event-free for service-to-service calls, while find / get / create / patch / remove do the same work and dispatch events. The codemod rewrites controllers from the first family to the second.

$cd my-app
 
# see every replacement first — nothing is written
$nest-cli m events --dry-run
 
# apply, after confirming
$nest-cli m events

The dry run prints each call site:

src/services/company/company.controller.ts
    _find -> find (line 24)
    _get -> get (line 31)
    ...

2 file(s), 10 replacement(s).

It only touches src/**/*.controller.ts by default, which is the point: an AuthService looking a user up with usersService._find(...) should not fire the users service’s onFind hook.

@Controller('company')
export class CompanyController {
  constructor(private readonly service: CompanyService) {}

  @Get()
  find(@Query() query: Record<string, any>) {
    return this.service._find(query);
  }

  @Post()
  create(@ModifyBody(setCreatedBy()) body: CreateCompanyDto) {
    return this.service._create(body);
  }
}

@Controller('company')
export class CompanyController {
  constructor(private readonly service: CompanyService) {}

  @Get()
  find(@Query() query: Record<string, any>) {
    return this.service.find(query);      // fires beforeFind / onFind
  }

  @Post()
  create(@ModifyBody(setCreatedBy()) body: CreateCompanyDto) {
    return this.service.create(body);     // fires beforeCreate / onCreate
  }
}

Step 4 makes hooks possible; nothing fires until a service has an events class. Generate one for a new resource with nest-cli g service (it is the default — --skip-events opts out), or write it by hand for an existing one.

import { Injectable } from '@nestjs/common';
import { EventContext, NestServiceEvents, ServiceEvents } from '@nest-extended/core';
import { CompanyService } from './company.service';
import { CompanyDocument } from '../../schemas/company.schema';

@Injectable()
@ServiceEvents(CompanyService)
export class CompanyEvents extends NestServiceEvents<CompanyService, CompanyDocument> {
  // Inline and awaited — what you return replaces the input.
  beforeCreate(data: any, ctx: EventContext<CompanyService>) {
    return { ...data, slug: slugify(data.name) };
  }

  // Detached — runs after the response has been sent.
  async onCreate(company: CompanyDocument, ctx: EventContext<CompanyService>) {
    await this.mailer.sendWelcome(company, ctx.user);
  }
}

Register it next to the service in the feature module’s providers — the generator does this for you:

@Module({
  imports: [MongooseModule.forFeature([{ name: Company.name, schema: CompanySchema }])],
  controllers: [CompanyController],
  providers: [CompanyService, CompanyEvents],   // <- both classes
})
export class CompanyModule {}

To broadcast events to other modules as well, install @nestjs/event-emitter, register EventEmitterModule.forRoot(), and construct the service with { broadcast: 'company' }. nest-cli g service --broadcast wires all three up for you. The full hook list, the context object and the limitations are in Service Events.