ReadonlycodeStable discriminant for programmatic handling; always "ENV_PROJECT_GENERATION_FAILED".
ReadonlyissuesEvery blocking finding, aggregated across all requested passes.
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
Thrown by generateEnvArtifacts when any requested pass (manifest/docs/usage) reports a blocking finding, aggregated across all requested passes into one error.
Remarks
Nothing from any pass is written when this throws -- see
generate-env-artifacts.ts's compute-atomic guarantee (ADR 0011). Write-phase failures (a real I/O error after all computes already passed) are NOT wrapped in this type -- they propagate as whateverfs.writeFileitself throws, since by that point some artifacts may already be on disk.codeis a stable, Stable-tier discriminant for programmatic handling -- prefer it over.name/instanceofwhen a message-independent switch is needed.