NestJS邮箱验证异常：含加号邮箱被判定无效

Hey there! Great question—this is a common gotcha when working with NestJS and email validation, especially since validator.js itself supports plus signs in email local parts by default. Let's break down what's happening and how to fix it without writing custom regex.

The Root Cause #

While validator.js (which powers NestJS's class-validator under the hood) allows plus signs in emails by default, the @IsEmail() decorator from class-validator might be using a different default configuration depending on your package version, or there could be a global validation setting overriding the expected behavior.

Specifically, some older versions of class-validator had allowPlusSign set to false by default (even though validator.js defaults to true), or your NestJS app's global validation pipe might be applying restrictive settings.

The Fix: Explicitly Enable Plus Sign Support in @IsEmail() #

You don't need custom regex—just pass the allowPlusSign: true option directly to the @IsEmail() decorator. This explicitly tells validator.js to allow plus signs in the local part of the email address.

Here's how to update your GetUserDto:

@Exclude()
export class GetUserDto {
  @Expose()
  id!: number;

  @Expose()
  @IsEmail({ allowPlusSign: true }) // Add this option to enable plus signs
  @IsNotEmpty()
  @ApiProperty({ 
    example: 'johndoe+tag@gmail.com', // Update example to reflect valid tagged email
    description: 'Username (email address)', 
  })
  username: string;
}

Additional Checks #

If the above fix doesn't work right away, double-check these two things:

• Update class-validator: Ensure you're using a recent version (v0.14.x or later). Older versions had inconsistent defaults for email validation options. Run npm update class-validator to get the latest stable release.
• Global Validation Pipe Configuration: If you've set up a global ValidationPipe in your main.ts, make sure it's not overriding email validation behaviors. Avoid any custom validation factories that might modify the default isEmail logic.

Why This Works #

By explicitly setting allowPlusSign: true, you bypass any default overrides from class-validator and directly enforce adherence to RFC standards that allow plus signs in email local parts—these are commonly used for email tagging, filtering, or testing purposes.

内容的提问来源于stack exchange，提问作者Amiga500