node:stream

#Import

import stream from "nstdlib/node/stream";

Note

Behaves like Node.js.

#Support

node:stream. nstd: some support; Node test suite 92.4% passing. Browser: works; export coverage 100%; Node test suite 90.7% passing.

  • nstd: 208/225 of Node's own eligible tests pass under nstd.
  • Browser: Loads with a minimal process object. 23 of Node's 23 exports are available. 1 of 1 behavior checks match Node.js.

#Exports (23)

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.jsBrowser
Duplex✅✅
PassThrough✅✅
Readable✅✅
Stream✅✅
Transform✅✅
Writable✅✅
_isArrayBufferView✅✅
_isUint8Array✅✅
_uint8ArrayToBuffer✅✅
addAbortSignal✅✅
compose✅✅
destroy✅✅
duplexPair✅✅
finished✅✅
getDefaultHighWaterMark✅✅
isDestroyed✅✅
isDisturbed✅✅
isErrored✅✅
isReadable✅✅
isWritable✅✅
pipeline✅✅
promises✅✅
setDefaultHighWaterMark✅✅

#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: 23/23 of the host's export names answer inside host node. Behaviour verified against the host builtin.
  • smoke: Imports in a clean child process.
  • node-suite: 202/226 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.