MissingTenantContextError

Defined in: packages/ddd-core/domain/exceptions/missing-tenant-context.exception.ts:23

Framework-neutral signal that an operation requiring tenant isolation was attempted without a resolvable tenant identity.

Tenant-scoped operations fail closed here. A missing tenant must never be collapsed into a shared or default tenant: every caller whose tenant could not be resolved would then read and write the same cache entries or database, which is a cross-tenant data leak that produces no error and no log line.

Deployments that are genuinely single-tenant make that explicit rather than implicit: pass a fixed tenant id to the key helper, or register setTenantResolver(() => 'single'), so the decision is visible in code.

Example

if (!tenantId) throw new MissingTenantContextError('users.create idempotency key');

Extends

DomainException

Constructors

Constructor

new MissingTenantContextError(operation): MissingTenantContextError

Defined in: packages/ddd-core/domain/exceptions/missing-tenant-context.exception.ts:24

Parameters

operation

string

Returns

MissingTenantContextError

Overrides

DomainException.constructor

Properties

cause?

optional cause?: unknown

Defined in: node_modules/.pnpm/typescript@6.0.3/node_modules/typescript/lib/lib.es2022.error.d.ts:24

Inherited from

DomainException.cause

message

message: string

Defined in: node_modules/.pnpm/typescript@6.0.3/node_modules/typescript/lib/lib.es5.d.ts:1075

Inherited from

DomainException.message

name

name: string

Defined in: node_modules/.pnpm/typescript@6.0.3/node_modules/typescript/lib/lib.es5.d.ts:1074

Inherited from

DomainException.name

operation

readonly operation: string

Defined in: packages/ddd-core/domain/exceptions/missing-tenant-context.exception.ts:24

stack?

optional stack?: string

Defined in: node_modules/.pnpm/typescript@6.0.3/node_modules/typescript/lib/lib.es5.d.ts:1076

Inherited from

DomainException.stack

stackTraceLimit

static stackTraceLimit: number

Defined in: node_modules/.pnpm/@types+node@26.6.3/node_modules/@types/node/globals.d.ts:67

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.

Inherited from

DomainException.stackTraceLimit

Methods

captureStackTrace()

static captureStackTrace(targetObject, constructorOpt?): void

Defined in: node_modules/.pnpm/@types+node@26.6.3/node_modules/@types/node/globals.d.ts:51

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