node:domain

#Import

import domain from "nstdlib/node/domain";

Note

The module loads, but its behavior hasn't been tested yet.

#Support

node:domain. nstd: some support; Node test suite 64.6% passing. Browser: unavailable; Node test suite 54.2% passing.

  • nstd: 31/48 of Node's own eligible tests pass under nstd.
  • Browser: Does not import in the browser realm: TypeError: process_default.on is not a function.

#Exports (5)

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.
ExportNode.js
Domain✅
_stack✅
active✅
create✅
createDomain✅

#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: 5/5 of the host's export names answer inside host node. Imports. Behaviour not exercised by the suite.
  • smoke: Imports in a clean child process.
  • node-suite: 32/50 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.