OptionalcauseReadonlyderivedReadonlykindDiscriminated tag for exhaustive matching.
ReadonlyreceivedOptionalstackStaticstackThe 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
Raised when a derived's
compute(get)callsgetwith a value that is not a live node handle:undefined,null, a primitive, or an object without a stringid.Remarks
The commonest way to reach this is a self-referential registration. The handle for the node being registered does not exist until
derived()returns, so a compute that closes over its own binding readsundefinedduring the eager first evaluation (and aconstself-reference dies earlier, in the temporal dead zone). The engine cannot call that a cycle:undefinedcarries no identity to match against the in-flight set. The adjacent arms of the taxonomy are already typed, and this class closes the gap between them: a read that names the id under registration through a live handle raises CycleError, a handle naming an id the graph has never seen raises UnknownNodeError, and a dynamic read of an unregistered id during a bridged recompute raises UndeclaredDependencyError (the sibling class with the same two-field shape).Before this class (causl/causl-wasm-ts#498),
get(undefined)andget(null)escaped as a raw hostTypeErrorwrapped in a generic DerivedComputeError, so an adopter branching on the tagged identity could not tell engine-detectable misuse from a bug in their own compute body; and every OTHER non-node argument (a plain object, a bare id string, a number, an object with a non-stringid) was misreported as UnknownNodeError for whatever its stray.idproperty happened to hold. Both shapes now classify here, which is a deliberate reclassification of that second group within the tagged taxonomy.Param: derivedId
The derived node whose compute performed the read.
Param: received
Printable description of the value
getreceived (see describeInvalidNodeHandle).