OptionalcauseReadonlyOperationThe operationName passed to WithTimeout.
OptionalstackReadonlyTimeoutThe budget that expired, in milliseconds.
StaticstackThe 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
The error WithTimeout rejects with when ITS OWN budget expires — as distinct from an error the wrapped operation itself produced.
That distinction is the whole point of the class.
ClassifyErrormaps anything matching "timeout" toNETWORK_TIMEOUT, whichIsRetryableErrortreats as transient — correct for a socket that dropped, wrong for "we gave this operation N ms and it wanted more." Retrying the latter re-runs the same work under the same budget, so it fails the same way, having spent the budget again.The message is deliberately UNCHANGED from the plain
Errorthis replaced:ClassifyErrorreads message text, so existing classification, logging and the run-event stream all behave exactly as before. Only callers that explicitly checkinstanceofsee any difference.