Node.js Client HTTP/HTTPS Request Wrapper

Common errors

• Error: require() of ES Module ... not supported

  cause Attempting to import `client-http` using `import` syntax in a Node.js ES Module project.
  fix This library is CommonJS-only. If you must use it (which is strongly discouraged), ensure your file is treated as CommonJS (e.g., `.js` file without `"type": "module"` in `package.json`) and use `const http = require('client-http');`.

• Error: ERR_OSSL_EVP_UNSUPPORTED

  cause Running `client-http` on modern Node.js versions (e.g., Node.js 17+) where legacy OpenSSL ciphers and hash functions used by the old library or its dependencies are disabled by default.
  fix This error signifies fundamental incompatibility with modern Node.js security standards. The only 'fix' is to *not use* this abandoned library. As a temporary workaround for *testing purposes only* (never in production), you can set `NODE_OPTIONS='--openssl-legacy-provider'` environment variable, but this significantly reduces security and does not resolve other issues.

• Error: The 'engines' field is defined with an unsupported Node.js version.

  cause Node Package Manager (npm) or Yarn attempting to install `client-http` when the current Node.js version falls outside the very narrow range specified in the `package.json` engines field (`>=0.6.11 <=0.7.0 || >=0.7.3`).
  fix This is an installation-time warning/error indicating the package is not designed for your Node.js version. It's a strong signal to *not* use this library. There is no practical fix for using it with modern Node.js.

Warnings

• breaking The package is explicitly abandoned and has not received updates since its final release (0.0.7). It is highly insecure due to unpatched vulnerabilities in its dependencies and its own codebase.
  Fix: Migrate to a actively maintained and secure HTTP client library like `axios`, `node-fetch`, or Node.js's built-in `http`/`https` modules.
• breaking This library is designed for extremely old Node.js versions (>=0.6.11 <=0.7.0 || >=0.7.3). It will not run correctly on modern Node.js versions (v10+, v12+, etc.) due to API changes, C++ addon incompatibilities, and updated security protocols.
  Fix: Do not use this package in any current or recent Node.js environment. It is incompatible and will cause runtime errors or unexpected behavior.
• gotcha The API is entirely callback-based, which is an outdated pattern for asynchronous operations. It does not support Promises or `async/await`, making integration into modern JavaScript codebases cumbersome.
  Fix: If migrating, adapt your logic to use modern async patterns (Promises, `async/await`) with a contemporary HTTP client library.
• gotcha Automatic proxy detection relies on the `http_proxy` environment variable. Manual proxy setting is global via `http.setProxy()`, not configurable per-request, which can be limiting for applications requiring fine-grained proxy control.
  Fix: For per-request proxy settings or more robust proxy management, a different library is required.

Install

• npm install client-http npm
• yarn add client-http yarn
• pnpm add client-http pnpm

Imports

• client-http
  wrong:

  import http from 'client-http';

  correct:

  const http = require('client-http');

  This library is CommonJS-only and does not support ES Modules syntax. Attempting to use `import` will result in a runtime error in modern Node.js.
• http.get
  wrong:

  import { get } from 'client-http';

  correct:

  const http = require('client-http');
  http.get('http://example.com', (data, err, cookie, headers) => { /* ... */ });

  Methods like `get` are exported as properties of the main `http` object, not as named exports from the module root.
• http.request
  wrong:

  import { request } from 'client-http';

  correct:

  const http = require('client-http');
  http.request('http://example.com', (data) => { /* ... */ }, 'body', { 'Content-Type': 'text/plain' });

  Similar to `get`, `request` is a method on the `http` object. It supports POST requests with body and custom headers.
• http.setProxy
  wrong:

  import { setProxy } from 'client-http';

  correct:

  const http = require('client-http');
  http.setProxy('http://127.0.0.1:8080');

  This function globally configures the proxy for subsequent requests. It's not a per-request option.

Quickstart

Demonstrates making basic HTTP GET requests to Google and Example.com, logging response data and showing how to set a global timeout.

const http = require('client-http');

// Make a simple HTTP GET request to Google
http.get("http://www.google.com/", function(data, err, cookie, headers){
    if (err) {
        console.error("Error:", err);
        return;
    }
    console.log("Response Data (truncated):");
    console.log(data ? data.substring(0, 200) + '...' : '[No Data]');
    console.log("Headers:", headers);
});

// Example of setting a timeout
http.setTimeout(5000); // Set timeout to 5 seconds
http.get("https://www.example.com/", function(data, err){
    if (err) {
        console.error("Timeout Error or other issue:", err);
        return;
    }
    console.log("Example.com response received within 5s.");
});