node:fs

#Import

import fs from "nstdlib/node/fs";

#Support

• nstd: Gives the same output as Node.js in side-by-side tests: fs, fs-watch.
• Browser: Loads with a minimal process object. 103 of Node's 103 exports are available. 1 of 1 behavior checks match Node.js.

#Exports (105)

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: 105/105 of the host's export names answer inside host node. Behaviour verified against the host builtin. Over a node:vfs memory mount. Paths outside a mount still throw.
• smoke: Imports in a clean child process.
• node-suite: 270/367 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.