Constructs a ConfigurationError.
Name of the module whose settings could not be resolved.
Optionalmessage: string
Full message. Defaults to one naming both likely causes.
ReadonlymoduleName of the module whose settings could not be resolved.
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
Error thrown when a module's settings were never registered.
Remarks
Two ways to get here, and they look identical at the call site, so the message names both:
configure()has not run. It goes once at startup, before anything that resolves settings is constructed. Usually a binding built at module scope instead of inside a handler.configure()seeds one copy whileresolve()reads the other and every lookup misses. Happens when a bundler inlines the kernel into an adapter package rather than leaving it external.The second is worth spelling out because nothing in the stack trace suggests a packaging problem.
Author
Bayu Dwiyan Satria
Version
1.0.0
Since
1.0.0