node:constants

#Import

import constants from "nstdlib/node/constants";

#Support

• nstd: 1/1 of Node's own eligible tests pass under nstd.
• Browser: Loads with a minimal process object. 240 of Node's 240 exports are available. No behavior check covers it yet.

#Exports (239)

Every name Node.js exports from this module, and what you get when you read it, as a named import or as a property of the default import:

• ✅ A value, both ways. An export that throws an error naming the missing feature also counts.
• ⚠️ A value one way, undefined the other.
• ❔ undefined both ways.
• ❌ Not exported at all.
• – Not measured.

#Diagnostics

nstdlib running inside Node.js. This isn't an environment it's meant for, so it isn't shown above, but it tells a library problem from an environment one:

• coverage: 239/239 of the host's export names answer inside host node. Behaviour verified against the host builtin. Every constant compared by value against the host builtin. The one difference is defaultCipherList, which real Node also has once crypto has been loaded first.
• smoke: Imports in a clean child process.
• node-suite: 1/1 of Node's own eligible tests pass with ./dist inside host node. A failure there and in the page is the library's, one only in the page is the engine's.