zod-nest 0.10.1 → 0.12.0

package/README.md

@@ -39,7 +39,7 @@ For the long-form motivation, see [`docs/why-this-exists.md`](docs/why-this-exis
 A short list of behavioural differences you'll hit on day one. Full migration table is in [`MIGRATION.md`](MIGRATION.md).
 
 - **Multi-status `@ZodResponse`** — stack the decorator per status code. In `nestjs-zod`, multi-status required mixing `@ZodSerializerDto` with hand-rolled `@ApiResponse({ status: ... })` calls.
-- **No internal `@HttpCode`** — `@ZodResponse` does **not** call `@HttpCode` under the hood. Status resolution precedence: `@ZodResponse({ status })` → `@HttpCode(...)` on the handler → method default (`POST → 201`, others → `200`). The caller controls `201` vs `200` vs `204` via standard NestJS decorators.
+- **No internal `@HttpCode`** — `@ZodResponse` does **not** call `@HttpCode` under the hood. Status resolution precedence: `@ZodResponse({ status })` → `@HttpCode(...)` on the handler → method default (`POST → 201`, others → `200`). The caller controls `201` vs `200` vs `204` via standard NestJS decorators. `status` accepts numeric codes plus the OpenAPI 3.1 range keys (`'1XX'`…`'5XX'`) and `'default'` (sugar for the resolved method default).
 - **I/O suffix only when needed** — `<Id>Output` is only emitted when the input and output JSON Schemas actually differ. `nestjs-zod` always emitted `_Output`.
 - **OpenAPI 3.1 only** — no `3.0` fallback. `$ref`s emit to the final location; `cleanupOpenApiDoc` is unnecessary.
 - **Validation-failure logging out of the box** — `nestjs-zod` has none.
@@ -52,7 +52,6 @@ A short list of behavioural differences you'll hit on day one. Full migration ta
 
 - **Zod v3 support** — Zod v4 only. Migrate first.
 - **`class-validator` / `class-transformer` coexistence** — `zod-nest` is Zod-native. Mixing class-validator decorators on a `createZodDto` result is not supported.
-- **Status wildcards** in `@ZodResponse` (`'2XX'`, `'default'`) — deferred to v1.
 - **Hybrid DTO projects** — mixing `createZodDto` DTOs with plain `@ApiProperty` classes in the same controller is not tested.
 - **Non-HTTP contexts** — WebSocket gateways, GraphQL resolvers, microservice handlers are out of scope.
 
@@ -423,7 +422,7 @@ A compact, link-out index. Type signatures and detailed semantics live in the co
 - `ZodValidationPipe`, `ZodValidationException`, `ZodValidationPipeOptions`, `CreateValidationException`
 
 **Response** — [`docs/responses.md`](docs/responses.md)
-- `@ZodResponse({ status?, type, description?, passthroughOnError? })`, `ZodSerializerInterceptor`, `ZodSerializationException`, `defaultStatusFor`, `resolveEffectiveStatus`, `ResponseVariant`, `ZOD_RESPONSES_METADATA_KEY`
+- `@ZodResponse({ status?, type, description?, passthroughOnError? })`, `ZodSerializerInterceptor`, `ZodSerializationException`, `defaultStatusFor`, `resolveEffectiveStatus`, `ResponseStatusInput`, `ResponseStatusWildcard`, `ResponseVariant`, `ZOD_RESPONSES_METADATA_KEY`
 
 **Document** — [`docs/swagger-integration.md`](docs/swagger-integration.md)
 - `applyZodNest(rawDoc, options)`, `ApplyZodNestOptions`, `ZodNestDocumentError`
@@ -449,6 +448,19 @@ A compact, link-out index. Type signatures and detailed semantics live in the co
 | Exception classes | [`docs/exceptions.md`](docs/exceptions.md) |
 | Recipes | [`docs/recipes/`](docs/recipes/) |
 
+## Compatibility matrix
+
+`zod-nest` declares broad peer-dep ranges in `package.json`: `zod >= 4.4.0`, `@nestjs/common >= 10`, `@nestjs/core >= 10`, `@nestjs/swagger >= 8`, `rxjs >= 7`, Node `>= 22`. CI validates those claims by running the full test suite against the cells below; a red cell is a real blocker.
+
+| Cell | `zod` | `@nestjs/common` | `@nestjs/core` | `@nestjs/swagger` |
+|---|---|---|---|---|
+| `floor` | 4.4.0 | 10.0.0 | 10.0.0 | 8.0.0 |
+| `zod-latest` | latest | 10.0.0 | 10.0.0 | 8.0.0 |
+| `nest-latest` | 4.4.0 | latest | latest | latest |
+| `all-latest` | latest | latest | latest | latest |
+
+Cell definitions live in [`.github/compat-matrix.json`](.github/compat-matrix.json). The CI workflow ([`.github/workflows/compat-matrix.yml`](.github/workflows/compat-matrix.yml)) runs on every push to `main` and weekly on Monday — when a cell fails, the workflow opens (or comments on) a GitHub issue labelled `compat-matrix-failure` so the regression is tracked outside the Actions UI. Editing the JSON is the formal way to extend or shrink supported ranges — Node + rxjs are not currently matrixed (Node floor `22` is enforced by `engines`; rxjs has been stable enough not to need cells yet).
+
 ## Migration from `nestjs-zod`
 
 If you're coming from `nestjs-zod`, the headline changes are:
@@ -457,7 +469,6 @@ If you're coming from `nestjs-zod`, the headline changes are:
 - Replace `@ApiOkResponse({ type: Dto }) + @ZodSerializerDto(Dto)` pairs with `@ZodResponse({ type: Dto })`.
 - Drop `class-validator` / `class-transformer` if they were installed only for `nestjs-zod` interop.
 - Check any `MyDto.isZodDto` reflection — the discriminator is now `Symbol.for('zod-nest.dto') in MyDto`.
-- Status wildcards (`'2XX'`, `'default'`) aren't supported in v0 — use explicit statuses.
 
 Full guide with side-by-side diffs and a 19-row breaking-changes table in [`MIGRATION.md`](MIGRATION.md).
 

package/dist/index.d.mts

@@ -321,6 +321,12 @@ declare class ZodValidationPipe implements PipeTransform {
  */
 declare const ZOD_RESPONSES_METADATA_KEY: unique symbol;
 type ResponseVariantKind = 'single' | 'array' | 'tuple';
+/**
+ * OpenAPI 3.1 range keys accepted by `@ZodResponse({ status })`. Matched
+ * by `ZodSerializerInterceptor` after exact numeric matches fail —
+ * `'2XX'` covers 200–299, `'4XX'` covers 400–499, and so on.
+ */
+type ResponseStatusWildcard = '1XX' | '2XX' | '3XX' | '4XX' | '5XX';
 /**
  * Description payload accepted by `@ZodResponse(...)` and passed through to
  * `applyZodNest`'s `@ApiResponse(...)` emitter. String form is shorthand for
@@ -337,14 +343,20 @@ type ZodResponseDescription = string | {
  * `validationSchema` so `applyZodNest` can emit `@ApiResponse({ type })`
  * without unwrapping the runtime-only `z.array(...)` / `z.tuple([...])` wrapper.
  *
- * `status` is `undefined` when the user didn't pass one explicitly — the
- * effective status is resolved lazily by `resolveEffectiveStatus(variant,
- * handler)` because `@ZodResponse` runs *before* NestJS' route decorators
- * (`@Get`, `@Post`, ...) under TypeScript's bottom-up application order,
- * so `METHOD_METADATA` is not yet set when the decorator evaluates.
+ * `status` is `undefined` when the user didn't pass one explicitly OR when
+ * the user wrote `'default'` (the decorator collapses both to `undefined` —
+ * they mean the same thing: "resolve to the method's default status at
+ * request time"). The effective status is resolved lazily by
+ * `resolveEffectiveStatus(variant, handler)` because `@ZodResponse` runs
+ * *before* NestJS' route decorators (`@Get`, `@Post`, ...) under
+ * TypeScript's bottom-up application order, so `METHOD_METADATA` is not
+ * yet set when the decorator evaluates.
+ *
+ * A wildcard string (`'2XX'` / `'4XX'` / ...) is kept verbatim — the
+ * matcher in `ZodSerializerInterceptor` handles range comparison.
  */
 interface ResponseVariant {
-    status: number | undefined;
+    status: number | ResponseStatusWildcard | undefined;
     kind: ResponseVariantKind;
     dto: ZodDto | readonly ZodDto[];
     validationSchema: z.ZodType;
@@ -365,8 +377,22 @@ interface ResponseVariant {
  * so typos surface at module load, not the first request.
  */
 type ZodResponseType = ZodDto | readonly [ZodDto, ...ZodDto[]];
+/**
+ * Accepted shapes for `@ZodResponse({ status })`:
+ * - `number` — exact match against `response.statusCode` (most common case).
+ * - `'1XX'` / `'2XX'` / `'3XX'` / `'4XX'` / `'5XX'` — OpenAPI 3.1 range key;
+ *   `'2XX'` matches 200–299, etc. Considered only after no exact numeric
+ *   variant matches the observed status.
+ * - `'default'` — sugar for the handler's method default status. Collapsed
+ *   to `undefined` when the variant is built, so `resolveEffectiveStatus`
+ *   walks the same `@HttpCode → method-default` chain as an omitted `status`.
+ *   This deliberately does NOT implement a catch-all-fallback semantic; it
+ *   names the canonical-success card explicitly, matching what consumers
+ *   already write in `@ApiResponse({ status: 'default' })`.
+ */
+type ResponseStatusInput = number | ResponseStatusWildcard | 'default';
 interface ZodResponseOptions {
-    status?: number;
+    status?: ResponseStatusInput;
     type: ZodResponseType;
     description?: ZodResponseDescription;
     passthroughOnError?: boolean;
@@ -374,7 +400,8 @@ interface ZodResponseOptions {
 /**
  * Method-only decorator. Declares a typed response variant for the handler.
  * Stack multiple decorations to declare per-status types; lookup at runtime
- * is by `response.statusCode === variant.status`.
+ * is by `ZodSerializerInterceptor`'s two-pass matcher (exact numeric, then
+ * `'NXX'` wildcard).
  *
  * The wrapped Zod schema (array / tuple) is built once at decoration time
  * and stored on the variant record — no per-request schema construction.
@@ -404,17 +431,19 @@ declare class ZodSerializerInterceptor implements NestInterceptor {
  */
 declare const defaultStatusFor: (handler: object) => number;
 /**
- * Resolve the effective status code for a variant. Precedence chain:
+ * Resolve the effective status for a variant. Precedence chain:
  *
- * 1. Explicit `@ZodResponse({ status })` on the decorator call — `variant.status`.
- * 2. `@HttpCode(n)` on the handler — read via `defaultStatusFor()` at runtime.
- * 3. HTTP method default (POST → 201, others → 200) — also via `defaultStatusFor()`.
+ * 1. Explicit numeric `@ZodResponse({ status })` — returned verbatim.
+ * 2. Wildcard `@ZodResponse({ status: 'NXX' })` — returned verbatim; the
+ *    interceptor matcher handles range comparison against `response.statusCode`.
+ * 3. Omitted status (or `'default'` collapsed at decoration time) —
+ *    `@HttpCode(n)` then HTTP-method default via `defaultStatusFor()`.
  *
  * Resolution is deferred to request time because `@ZodResponse` runs before
  * NestJS' route + `@HttpCode` decorators — none of their metadata is set
  * when the decorator evaluates.
  */
-declare const resolveEffectiveStatus: (variant: ResponseVariant, handler: object) => number;
+declare const resolveEffectiveStatus: (variant: ResponseVariant, handler: object) => number | ResponseStatusWildcard;
 
 /**
  * Central wiring for the zod-nest pipe + interceptor. Call
@@ -498,4 +527,4 @@ declare class ZodNestDocumentError extends ZodNestError {
     constructor(code: ZodNestDocumentErrorCode, message: string, details?: Record<string, unknown>);
 }
 
-export { type ApplyZodNestOptions, COMPONENTS_SCHEMAS_PREFIX, type CreateSerializationException, type CreateValidationException, type CreateZodDtoOptions, DEFAULT_MAX_LOGGED_VALUE_BYTES, DEFAULT_REDACT_KEYS, type Io, type LineageEntry, type NormalizedZodNestOptions, type Override, type OverrideContext, type ResponseVariant, type ResponseVariantKind, type SchemaObject, type ToOpenApiOptions, type ToOpenApiResult, ZOD_DTO_SYMBOL, ZOD_NEST_DTO_EXTENSION, ZOD_NEST_ERROR_DUPLICATE_ID, ZOD_NEST_ERROR_EXTENSION, ZOD_NEST_OPTIONS, ZOD_RESPONSES_METADATA_KEY, type ZodDto, type ZodDtoMarker, ZodNestDocumentError, type ZodNestDocumentErrorCode, ZodNestError, ZodNestModule, type ZodNestModuleOptions, type ZodNestRegistry, ZodNestUnrepresentableError, ZodResponse, type ZodResponseDescription, type ZodResponseOptions, type ZodResponseType, ZodSerializationException, ZodSerializerInterceptor, ZodValidationException, ZodValidationPipe, type ZodValidationPipeArg, type ZodValidationPipeOptions, applyZodNest, createRegistry, createZodDto, defaultRegistry, defaultStatusFor, extend, getLineage, isZodDto, isZodDtoMarker, makeZodDtoMarker, resolveEffectiveStatus, toOpenApi };
+export { type ApplyZodNestOptions, COMPONENTS_SCHEMAS_PREFIX, type CreateSerializationException, type CreateValidationException, type CreateZodDtoOptions, DEFAULT_MAX_LOGGED_VALUE_BYTES, DEFAULT_REDACT_KEYS, type Io, type LineageEntry, type NormalizedZodNestOptions, type Override, type OverrideContext, type ResponseStatusInput, type ResponseStatusWildcard, type ResponseVariant, type ResponseVariantKind, type SchemaObject, type ToOpenApiOptions, type ToOpenApiResult, ZOD_DTO_SYMBOL, ZOD_NEST_DTO_EXTENSION, ZOD_NEST_ERROR_DUPLICATE_ID, ZOD_NEST_ERROR_EXTENSION, ZOD_NEST_OPTIONS, ZOD_RESPONSES_METADATA_KEY, type ZodDto, type ZodDtoMarker, ZodNestDocumentError, type ZodNestDocumentErrorCode, ZodNestError, ZodNestModule, type ZodNestModuleOptions, type ZodNestRegistry, ZodNestUnrepresentableError, ZodResponse, type ZodResponseDescription, type ZodResponseOptions, type ZodResponseType, ZodSerializationException, ZodSerializerInterceptor, ZodValidationException, ZodValidationPipe, type ZodValidationPipeArg, type ZodValidationPipeOptions, applyZodNest, createRegistry, createZodDto, defaultRegistry, defaultStatusFor, extend, getLineage, isZodDto, isZodDtoMarker, makeZodDtoMarker, resolveEffectiveStatus, toOpenApi };

package/dist/index.d.ts

@@ -321,6 +321,12 @@ declare class ZodValidationPipe implements PipeTransform {
  */
 declare const ZOD_RESPONSES_METADATA_KEY: unique symbol;
 type ResponseVariantKind = 'single' | 'array' | 'tuple';
+/**
+ * OpenAPI 3.1 range keys accepted by `@ZodResponse({ status })`. Matched
+ * by `ZodSerializerInterceptor` after exact numeric matches fail —
+ * `'2XX'` covers 200–299, `'4XX'` covers 400–499, and so on.
+ */
+type ResponseStatusWildcard = '1XX' | '2XX' | '3XX' | '4XX' | '5XX';
 /**
  * Description payload accepted by `@ZodResponse(...)` and passed through to
  * `applyZodNest`'s `@ApiResponse(...)` emitter. String form is shorthand for
@@ -337,14 +343,20 @@ type ZodResponseDescription = string | {
  * `validationSchema` so `applyZodNest` can emit `@ApiResponse({ type })`
  * without unwrapping the runtime-only `z.array(...)` / `z.tuple([...])` wrapper.
  *
- * `status` is `undefined` when the user didn't pass one explicitly — the
- * effective status is resolved lazily by `resolveEffectiveStatus(variant,
- * handler)` because `@ZodResponse` runs *before* NestJS' route decorators
- * (`@Get`, `@Post`, ...) under TypeScript's bottom-up application order,
- * so `METHOD_METADATA` is not yet set when the decorator evaluates.
+ * `status` is `undefined` when the user didn't pass one explicitly OR when
+ * the user wrote `'default'` (the decorator collapses both to `undefined` —
+ * they mean the same thing: "resolve to the method's default status at
+ * request time"). The effective status is resolved lazily by
+ * `resolveEffectiveStatus(variant, handler)` because `@ZodResponse` runs
+ * *before* NestJS' route decorators (`@Get`, `@Post`, ...) under
+ * TypeScript's bottom-up application order, so `METHOD_METADATA` is not
+ * yet set when the decorator evaluates.
+ *
+ * A wildcard string (`'2XX'` / `'4XX'` / ...) is kept verbatim — the
+ * matcher in `ZodSerializerInterceptor` handles range comparison.
  */
 interface ResponseVariant {
-    status: number | undefined;
+    status: number | ResponseStatusWildcard | undefined;
     kind: ResponseVariantKind;
     dto: ZodDto | readonly ZodDto[];
     validationSchema: z.ZodType;
@@ -365,8 +377,22 @@ interface ResponseVariant {
  * so typos surface at module load, not the first request.
  */
 type ZodResponseType = ZodDto | readonly [ZodDto, ...ZodDto[]];
+/**
+ * Accepted shapes for `@ZodResponse({ status })`:
+ * - `number` — exact match against `response.statusCode` (most common case).
+ * - `'1XX'` / `'2XX'` / `'3XX'` / `'4XX'` / `'5XX'` — OpenAPI 3.1 range key;
+ *   `'2XX'` matches 200–299, etc. Considered only after no exact numeric
+ *   variant matches the observed status.
+ * - `'default'` — sugar for the handler's method default status. Collapsed
+ *   to `undefined` when the variant is built, so `resolveEffectiveStatus`
+ *   walks the same `@HttpCode → method-default` chain as an omitted `status`.
+ *   This deliberately does NOT implement a catch-all-fallback semantic; it
+ *   names the canonical-success card explicitly, matching what consumers
+ *   already write in `@ApiResponse({ status: 'default' })`.
+ */
+type ResponseStatusInput = number | ResponseStatusWildcard | 'default';
 interface ZodResponseOptions {
-    status?: number;
+    status?: ResponseStatusInput;
     type: ZodResponseType;
     description?: ZodResponseDescription;
     passthroughOnError?: boolean;
@@ -374,7 +400,8 @@ interface ZodResponseOptions {
 /**
  * Method-only decorator. Declares a typed response variant for the handler.
  * Stack multiple decorations to declare per-status types; lookup at runtime
- * is by `response.statusCode === variant.status`.
+ * is by `ZodSerializerInterceptor`'s two-pass matcher (exact numeric, then
+ * `'NXX'` wildcard).
  *
  * The wrapped Zod schema (array / tuple) is built once at decoration time
  * and stored on the variant record — no per-request schema construction.
@@ -404,17 +431,19 @@ declare class ZodSerializerInterceptor implements NestInterceptor {
  */
 declare const defaultStatusFor: (handler: object) => number;
 /**
- * Resolve the effective status code for a variant. Precedence chain:
+ * Resolve the effective status for a variant. Precedence chain:
  *
- * 1. Explicit `@ZodResponse({ status })` on the decorator call — `variant.status`.
- * 2. `@HttpCode(n)` on the handler — read via `defaultStatusFor()` at runtime.
- * 3. HTTP method default (POST → 201, others → 200) — also via `defaultStatusFor()`.
+ * 1. Explicit numeric `@ZodResponse({ status })` — returned verbatim.
+ * 2. Wildcard `@ZodResponse({ status: 'NXX' })` — returned verbatim; the
+ *    interceptor matcher handles range comparison against `response.statusCode`.
+ * 3. Omitted status (or `'default'` collapsed at decoration time) —
+ *    `@HttpCode(n)` then HTTP-method default via `defaultStatusFor()`.
  *
  * Resolution is deferred to request time because `@ZodResponse` runs before
  * NestJS' route + `@HttpCode` decorators — none of their metadata is set
  * when the decorator evaluates.
  */
-declare const resolveEffectiveStatus: (variant: ResponseVariant, handler: object) => number;
+declare const resolveEffectiveStatus: (variant: ResponseVariant, handler: object) => number | ResponseStatusWildcard;
 
 /**
  * Central wiring for the zod-nest pipe + interceptor. Call
@@ -498,4 +527,4 @@ declare class ZodNestDocumentError extends ZodNestError {
     constructor(code: ZodNestDocumentErrorCode, message: string, details?: Record<string, unknown>);
 }
 
-export { type ApplyZodNestOptions, COMPONENTS_SCHEMAS_PREFIX, type CreateSerializationException, type CreateValidationException, type CreateZodDtoOptions, DEFAULT_MAX_LOGGED_VALUE_BYTES, DEFAULT_REDACT_KEYS, type Io, type LineageEntry, type NormalizedZodNestOptions, type Override, type OverrideContext, type ResponseVariant, type ResponseVariantKind, type SchemaObject, type ToOpenApiOptions, type ToOpenApiResult, ZOD_DTO_SYMBOL, ZOD_NEST_DTO_EXTENSION, ZOD_NEST_ERROR_DUPLICATE_ID, ZOD_NEST_ERROR_EXTENSION, ZOD_NEST_OPTIONS, ZOD_RESPONSES_METADATA_KEY, type ZodDto, type ZodDtoMarker, ZodNestDocumentError, type ZodNestDocumentErrorCode, ZodNestError, ZodNestModule, type ZodNestModuleOptions, type ZodNestRegistry, ZodNestUnrepresentableError, ZodResponse, type ZodResponseDescription, type ZodResponseOptions, type ZodResponseType, ZodSerializationException, ZodSerializerInterceptor, ZodValidationException, ZodValidationPipe, type ZodValidationPipeArg, type ZodValidationPipeOptions, applyZodNest, createRegistry, createZodDto, defaultRegistry, defaultStatusFor, extend, getLineage, isZodDto, isZodDtoMarker, makeZodDtoMarker, resolveEffectiveStatus, toOpenApi };
+export { type ApplyZodNestOptions, COMPONENTS_SCHEMAS_PREFIX, type CreateSerializationException, type CreateValidationException, type CreateZodDtoOptions, DEFAULT_MAX_LOGGED_VALUE_BYTES, DEFAULT_REDACT_KEYS, type Io, type LineageEntry, type NormalizedZodNestOptions, type Override, type OverrideContext, type ResponseStatusInput, type ResponseStatusWildcard, type ResponseVariant, type ResponseVariantKind, type SchemaObject, type ToOpenApiOptions, type ToOpenApiResult, ZOD_DTO_SYMBOL, ZOD_NEST_DTO_EXTENSION, ZOD_NEST_ERROR_DUPLICATE_ID, ZOD_NEST_ERROR_EXTENSION, ZOD_NEST_OPTIONS, ZOD_RESPONSES_METADATA_KEY, type ZodDto, type ZodDtoMarker, ZodNestDocumentError, type ZodNestDocumentErrorCode, ZodNestError, ZodNestModule, type ZodNestModuleOptions, type ZodNestRegistry, ZodNestUnrepresentableError, ZodResponse, type ZodResponseDescription, type ZodResponseOptions, type ZodResponseType, ZodSerializationException, ZodSerializerInterceptor, ZodValidationException, ZodValidationPipe, type ZodValidationPipeArg, type ZodValidationPipeOptions, applyZodNest, createRegistry, createZodDto, defaultRegistry, defaultStatusFor, extend, getLineage, isZodDto, isZodDtoMarker, makeZodDtoMarker, resolveEffectiveStatus, toOpenApi };

package/dist/index.js

@@ -801,15 +801,22 @@ var buildKind = /* @__PURE__ */ __name((type) => {
     validationSchema: type.schema
   };
 }, "buildKind");
+var normaliseStatus = /* @__PURE__ */ __name((status) => {
+  if (status === "default") {
+    return void 0;
+  }
+  return status;
+}, "normaliseStatus");
 var ZodResponse = /* @__PURE__ */ __name((opts) => {
   const built = buildKind(opts.type);
+  const status = normaliseStatus(opts.status);
   return (_target, _propertyKey, descriptor) => {
     const handler = descriptor.value;
     if (typeof handler !== "function") {
       throw new TypeError("[zod-nest] @ZodResponse can only be applied to methods.");
     }
     const variant = {
-      status: opts.status,
+      status,
       kind: built.kind,
       dto: built.dto,
       validationSchema: built.validationSchema,
@@ -866,6 +873,22 @@ var formatDtoLabel = /* @__PURE__ */ __name((variant) => {
   return `[${dtos.map((d) => d.name).join(", ")}]`;
 }, "formatDtoLabel");
 var formatHandlerLabel = /* @__PURE__ */ __name((context) => `${context.getClass().name}.${context.getHandler().name}`, "formatHandlerLabel");
+var matchesWildcard = /* @__PURE__ */ __name((wildcard, status) => wildcard.charCodeAt(0) - 48 === Math.floor(status / 100), "matchesWildcard");
+var selectVariant = /* @__PURE__ */ __name((variants, status, handler) => {
+  for (const variant of variants) {
+    const effective = resolveEffectiveStatus(variant, handler);
+    if (typeof effective === "number" && effective === status) {
+      return variant;
+    }
+  }
+  for (const variant of variants) {
+    const effective = resolveEffectiveStatus(variant, handler);
+    if (typeof effective === "string" && matchesWildcard(effective, status)) {
+      return variant;
+    }
+  }
+  return void 0;
+}, "selectVariant");
 exports.ZodSerializerInterceptor = class ZodSerializerInterceptor {
   static {
     __name(this, "ZodSerializerInterceptor");
@@ -895,7 +918,7 @@ exports.ZodSerializerInterceptor = class ZodSerializerInterceptor {
     if (status === void 0) {
       return value;
     }
-    const variant = variants.find((v) => resolveEffectiveStatus(v, handler) === status);
+    const variant = selectVariant(variants, status, handler);
     if (variant === void 0) {
       return value;
     }