Skip to content

bpmn-server / EngineNotRunningError

Class: EngineNotRunningError#

Running or testing a process, when nothing can run it: the rest (models, their history, their checks) goes on.

Hierarchy#

  • Error

↳ EngineNotRunningError

Table of contents#

Constructors#

Properties#

Methods#

Constructors#

constructor#

• new EngineNotRunningError(why?): EngineNotRunningError

Parameters#

Name Type Default value
why string 'none is running here'

Returns#

EngineNotRunningError

Overrides#

Error.constructor

Defined in#

packages/bpmn-server/src/server/LaunchedServer.ts:10

Properties#

cause#

• Optional cause: unknown

Inherited from#

Error.cause

Defined in#

docs/node_modules/typescript/lib/lib.es2022.error.d.ts:24

name#

• name: string

Inherited from#

Error.name

Defined in#

docs/node_modules/typescript/lib/lib.es5.d.ts:1076

message#

• message: string

Inherited from#

Error.message

Defined in#

docs/node_modules/typescript/lib/lib.es5.d.ts:1077

stack#

• Optional stack: string

Inherited from#

Error.stack

Defined in#

docs/node_modules/typescript/lib/lib.es5.d.ts:1078

stackTraceLimit#

▪ Static stackTraceLimit: number

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#

Error.stackTraceLimit

Defined in#

node_modules/@types/node/globals.d.ts:67

code#

• Readonly code: "ENGINE_NOT_RUNNING"

Defined in#

packages/bpmn-server/src/server/LaunchedServer.ts:9

Methods#

captureStackTrace#

▸ captureStackTrace(targetObject, constructorOpt?): void

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

Parameters#

Name Type
targetObject object
constructorOpt? Function

Returns#

void

Inherited from#

Error.captureStackTrace

Defined in#

node_modules/@types/node/globals.d.ts:51

prepareStackTrace#

▸ prepareStackTrace(err, stackTraces): any

Parameters#

Name Type
err Error
stackTraces CallSite[]

Returns#

any

See

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

Inherited from#

Error.prepareStackTrace

Defined in#

node_modules/@types/node/globals.d.ts:55

Comments