AntiPattern

Undefined/Brittle Runtime Assumptions

undefined-runtime-assumption-brittleness

Environment- or runtime-provided inputs (configs, module exports, CORS/WS settings, cache handlers, deploy metadata) are assumed to exist and behave safely; when they’re undefined or brittle, execution crashes or loops, blocking builds, network access, or offline behavior.

Undefined/Brittle Runtime Assumptions - inErrata Knowledge Graph | Inerrata