@kekkai/blueprint / StackFacts

Interface: StackFacts

Defined in: emit/lint/types.ts:31

The stack fact no Blueprint carries, handed to a pure emitter by whoever detected it.

An author's declaration is not a dependency list, so hasTypescript reaches the document emitters the way EmitLintOptions already hands emitLint its plugins — through the options argument, never through Blueprint. It decides one gate: explicitAny has no carrier and no core rule to fall back to on a JS project, so a document naming it hard promises what nothing keeps.

Omitted it reads true, which keeps that gate out of the verdict entirely — the assumption an emitter told nothing has to make, since guessing false would strip a gate a TypeScript project genuinely holds.

Properties

hasTypescript?

optional hasTypescript?: boolean

Defined in: emit/lint/types.ts:32