# node:_http_client

<!-- Generated from reports/manifest.json by `node ./scripts/api-docs.ts`.
     Do not edit this file. Run `pnpm run docs` to rebuild it.
     Node v26.10.0, commit 3b8da01340e75343534959df5c10dbb9d92a7d18. -->

# `node:_http_client`

## Import

```js
import _http_client from "nstdlib/node/_http_client";
```

> [!NOTE]
> The module loads, but its behavior hasn't been tested yet.

## Support

![node:_http_client. nstd: not measured. Browser: not tested; export coverage 100%.](/api-charts/module/internal_http_client.svg)

- **nstd:** Not measured in this environment.
- **Browser:** Loads with a minimal `process` object. 1 of Node's 1 exports are available. No behavior check covers it yet.

## 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.

| Export | Node.js | Browser |
| ------ | ------- | ------- |
| `ClientRequest` | <span title="Available" aria-label="Available">✅</span> | <span title="Available" aria-label="Available">✅</span> |

## 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. Imports. Behaviour not exercised by the suite.
- **`smoke`:** Imports in a clean child process.