node:stream/promises
#Import
import stream_promises from "nstdlib/node/stream/promises";Note
Behaves like Node.js.
#Support
- nstd: 208/225 of Node's own eligible tests pass under nstd (filed under
stream, the parent module). - Browser: Loads with a minimal
processobject. 2 of Node's 2 exports are available. No behavior check covers it yet.
#Exports (2)
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,
undefinedthe other. - ❔
undefinedboth ways. - ❌ Not exported at all.
- – Not measured.
| Export | Node.js | Browser |
|---|---|---|
finished | ✅ | ✅ |
pipeline | ✅ | ✅ |
#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: 2/2 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 (filed understream, the parent module).