Skip to content

ConnectorSupersededError

Defined in: packages/client/src/lib/orchestrator/connector-superseded-error.ts:16

Thrown by Orchestrator.processIntent when a concurrent Orchestrator.setConnector superseded the request while it was in flight.

The response the outgoing connector produced is deliberately never dispatched, so resolving with it would hand the caller a userMessage describing a board that never moved — a realtime voice session would speak it aloud while the UI sat still. Rejecting instead makes the discard observable: useMaelstrom surfaces it through lastError / onError, and callers instanceof-match it to re-issue the intent against the new connector rather than treating it as a processing failure.

  • MaelstromError

new ConnectorSupersededError(): ConnectorSupersededError

Defined in: packages/client/src/lib/orchestrator/connector-superseded-error.ts:17

ConnectorSupersededError

MaelstromError.constructor

readonly optional cause?: unknown

Defined in: packages/protocol/dist/lib/errors/base.d.ts:12

MaelstromError.cause


readonly code: string

Defined in: packages/protocol/dist/lib/errors/base.d.ts:11

MaelstromError.code


message: string

Defined in: node_modules/.bun/typescript@5.9.3/node_modules/typescript/lib/lib.es5.d.ts:1077

MaelstromError.message


name: string

Defined in: node_modules/.bun/typescript@5.9.3/node_modules/typescript/lib/lib.es5.d.ts:1076

MaelstromError.name


optional stack?: string

Defined in: node_modules/.bun/typescript@5.9.3/node_modules/typescript/lib/lib.es5.d.ts:1078

MaelstromError.stack


static stackTraceLimit: number

Defined in: node_modules/.bun/@types+node@24.13.3/node_modules/@types/node/globals.d.ts:68

The 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.

MaelstromError.stackTraceLimit

static captureStackTrace(targetObject, constructorOpt?): void

Defined in: node_modules/.bun/@types+node@24.13.3/node_modules/@types/node/globals.d.ts:52

Creates 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();

object

Function

void

MaelstromError.captureStackTrace


static prepareStackTrace(err, stackTraces): any

Defined in: node_modules/.bun/@types+node@24.13.3/node_modules/@types/node/globals.d.ts:56

Error

CallSite[]

any

https://v8.dev/docs/stack-trace-api#customizing-stack-traces

MaelstromError.prepareStackTrace