ValidationPipe still uses class-validator package

You can start using forks now in the following way:

app.useGlobalPipes(new ValidationPipe(
  {
    validatorPackage: require('@nestjs/class-validator'),
    transformerPackage: require('@nestjs/class-transformer')
  }
));

We’ll keep using the original packages for the time being till we figure out what’s the best approach to migrate.

It would be a breaking change to just swap out class-validator for @nestjs/class-valdator because there’s nothing in the update that would tell npm/yarn/pnpm that a new package would be necessary to download, so people updating package versions would now get this new error seemingly out of nowhere on a minor update. We could do a multi-step try/catch, i.e. try for @nestjs/class-validator catch try class-validator catch throw error, but the less optional package requires we have, usually the better (it’ll also mean needing to update our webpack config in nest-cli to exclude the @nestjs/class-validator and @nestjs/class-transformer packages).

My plans would be to hold out until Nest v9 and have the forked package ready and maintained, and give instructions for how people could override the default if they wanted to, essentially making it opt-in until v9. Something like

@Injectable()
export class NestValidationPipe extends ValidationPipe {
  loadValidator() {
    return require('@nestjs/class-validator');
  }

  loadTransformer() {
    return require('@nestjs/class-transformer');
  }
}

Would be all that’s necessary to use this package (if it’s been published of course, I haven’t checked that part yet)