node:string_decoder

#Import

import string_decoder from "nstdlib/node/string_decoder";

Note

Behaves like Node.js.

#Support

node:string_decoder. nstd: not measured. Browser: works; export coverage 100%.

  • nstd: Not measured in this environment.
  • Browser: Loads with a minimal process object. 1 of Node's 1 exports are available. 1 of 1 behavior checks match Node.js.

#Exports (1)

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
StringDecoder✅✅

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