Builds the error from the validator's message, the boundary
context label, and (typically) the validator's error as the cause.
Human-readable error description.
Boundary label plus optional cause.
Optionalcause?: unknownOriginal error (typically a ZodError).
Boundary the rejected payload came from.
OptionalcauseReadonlycontextReadonlynameOptionalstackStaticstackThe Error.stackTraceLimit property specifies the number of stack frames
collected by a stack trace (whether generated by new Error().stack or
Error.captureStackTrace(obj)).
The default value is 10 but may be set to any valid JavaScript number. Changes
will affect any stack trace captured after the value has been changed.
If set to a non-number value, or set to a negative number, stack traces will not capture any frames.
StaticcaptureCreates a .stack property on targetObject, which when accessed returns
a string representing the location in the code at which
Error.captureStackTrace() was called.
const myObject = {};
Error.captureStackTrace(myObject);
myObject.stack; // Similar to `new Error().stack`
The first line of the trace will be prefixed with
${myObject.name}: ${myObject.message}.
The optional constructorOpt argument accepts a function. If given, all frames
above constructorOpt, including constructorOpt, will be omitted from the
generated stack trace.
The constructorOpt argument is useful for hiding implementation
details of error generation from the user. For instance:
function a() {
b();
}
function b() {
c();
}
function c() {
// Create an error without stack trace to avoid calculating the stack trace twice.
const { stackTraceLimit } = Error;
Error.stackTraceLimit = 0;
const error = new Error();
Error.stackTraceLimit = stackTraceLimit;
// Capture the stack trace above function b
Error.captureStackTrace(error, b); // Neither function c, nor b is included in the stack trace
throw error;
}
a();
OptionalconstructorOpt: FunctionStaticisIndicates whether the argument provided is a built-in Error instance or not.
Staticprepare
Thrown when a runtime validator rejects an upstream payload. The consuming SDKs construct it at their zod boundaries (
parseOrThrow, which stays in each SDK); the class itself names no validator — the validator's own error, typically aZodError, rides the standardcausechain asunknown. Thecontextfield surfaces which boundary the payload came from (an endpoint or flow label such as'login'or'BFF /context') so consumer dashboards can group drift alerts without parsing the message string.