ReadonlybridgeThe resolved bridge the conflicting re-preload targeted.
OptionalcauseReadonlycodeReadonlyconflictingThe option names whose values differ from the first preload.
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
#144 — thrown by preloadCauslWasm when a bridge is re-preloaded with artefact-resolution options (
wasmBaseUrl/computeImportsUrl/fetch) that CONFLICT with the options the bridge was FIRST preloaded under.The preload cache is keyed by resolved BridgeId and holds the FIRST caller's resolved handle (the compiled module + snippet). Before this guard, a second
preloadCauslWasm({ wasmBaseUrl: B })after apreloadCauslWasm({ wasmBaseUrl: A })short-circuited on the bridge key and SILENTLY returned A's bytes — the differing artefact location / fetch was dropped without a sound. (Per-graph params —graphName/engine/batchedFlush/ retention caps — are NOT a conflict: #82 hascreateCauslWasmre-apply its own on every call, so they may legitimately differ across calls on one bridge.)Re-preloading with the SAME options stays idempotent (the shared resolution is returned, unchanged); only a CONFLICTING re-preload is rejected loudly so the caller learns their second location/fetch/params were never honored. The remedy is to reset in-process (the artefact for a given bridge is fixed for the process lifetime) or to pin a DISTINCT
bridgeper artefact location.Subclass of CauslError; branch on
error.code === 'CAUSL_WASM_PRELOAD_CONFLICT'.