node:console

#Import

import console from "nstdlib/node/console";

#Support

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

#Exports (31)

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: 31/31 of the host's export names answer inside host node. Behaviour verified against the host builtin. The whole namespace is diffed in child realms, writes to process.stdout/stderr included. The five inspector names answer what the host answers with no debugger attached. profile, profileEnd, timeStamp and context accept and drop, and createTask runs its callback for real.
• smoke: Imports in a clean child process.
• node-suite: 18/22 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.