Creates the error. The message is the full diagnostic — safe to log,
never to serve.
The full diagnostic, safe to log
Optionaloptions: { cause?: unknown }
The original driver error, preserved as cause
OptionalcauseReadonlynameDiscriminant for consumers that cannot use instanceof across realms.
OptionalstackStaticstackThe 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: FunctionStaticprepare
Thrown when the database, its connection pool, or its network is temporarily unreachable (X35-2, M90f). The operation did not happen and may be retried.
The condition reaches the client as
503 Service Unavailable— the load-shedding status — instead of a masked500. NoRetry-Afteris carried, and the hint channel cannot carry one:ErrorResponseInithas no header channel, and the framework holds no honest value to invent — a pool's saturation has no published horizon.503is itself the retryable signal (RFC 9110), and the rate limiter'sRetry-After(which does know its reset point) is the deliberate asymmetry, recorded inPUBLIC_API.md.Example
Since
0.5.0