node:_http_server
#Import
import _http_server from "nstdlib/node/_http_server";Note
The module loads, but its behavior hasn't been tested yet.
#Support
- nstd: Not measured in this environment.
- Browser: Loads with a minimal
processobject. 9 of Node's 9 exports are available. No behavior check covers it yet.
#Exports (9)
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 |
|---|---|---|
STATUS_CODES | ✅ | ✅ |
Server | ✅ | ✅ |
ServerResponse | ✅ | ✅ |
_connectionListener | ✅ | ✅ |
httpServerPreClose | ✅ | ✅ |
kConnectionsCheckingInterval | ✅ | ✅ |
kServerResponse | ✅ | ✅ |
setupConnectionsTracking | ✅ | ✅ |
storeHTTPOptions | ✅ | ✅ |
#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: 9/9 of the host's export names answer inside host node. Imports. Behaviour not exercised by the suite.smoke: Imports in a clean child process.