tcmts.core.effects

EFFECT_EXPORTS Record<string, Effect>

Exports of Node's other modules that reach outside: `module#export`.

EFFECT_GLOBALS Record<string, Effect>

Globals that reach outside, whatever's done with them.

EFFECT_MEMBERS Record<string, Effect>

Members of globals (and of Node modules imported whole) that reach outside: `Global.member`.

EFFECT_MODULES Record<string, Effect>

Node's modules that reach outside, as a whole (any use of them), and what they reach.

Effect type

What code can reach outside the codebase, so that running it twice can give different answers: the time, random numbers, the network, files, the machine and process it runs in (its environment variables, platform, working directory), and other processes; and what it writes out (`console`), which a value kept rather than computed wouldn't.

QUIET_PROCESS Set<string>

`process`'s members that don't reach outside: exiting, and listening.

ownEffects (ir: unknown) => Effect[]

What one definition's own code (its stored IR) reaches outside the codebase, not counting what it uses: from Node's modules it imports, the globals it reads (`fetch`, `process.env`, `Date.now()`, `new Date()`, `Math.random()`), and which of their members. What's only named in types (`b: Buffer`, `typeof process` in a type, a type imported from `node:fs`) is erased, so it reaches nothing. What npm packages do inside isn't seen.

testOwnEffects () => void