node:stream/web

#Import

import stream_web from "nstdlib/node/stream/web";

Note

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

#Support

node:stream/web. 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 (filed under stream, the parent module).
  • Browser: Loads with a minimal process object. 18 of Node's 18 exports are available. 1 of 1 behavior checks match Node.js.

#Exports (18)

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
ByteLengthQueuingStrategy✅✅
CompressionStream✅✅
CountQueuingStrategy✅✅
DecompressionStream✅✅
ReadableByteStreamController✅✅
ReadableStream✅✅
ReadableStreamBYOBReader✅✅
ReadableStreamBYOBRequest✅✅
ReadableStreamDefaultController✅✅
ReadableStreamDefaultReader✅✅
ReadableStreamTee✅✅
TextDecoderStream✅✅
TextEncoderStream✅✅
TransformStream✅✅
TransformStreamDefaultController✅✅
WritableStream✅✅
WritableStreamDefaultController✅✅
WritableStreamDefaultWriter✅✅

#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: 18/18 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: 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 (filed under stream, the parent module).