canirequire › CommonJS › proxy-addr
Is proxy-addr ESM-only? Can you require() it?
Determine address of proxied request
Last verified Sep 9, 2026 against proxy-addr@2.0.7. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
proxy-addr ships CommonJS only. require("proxy-addr") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.10. import "proxy-addr" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.
What to do
- require("proxy-addr") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.10.
- From ES modules use the default import: import proxyAddr from "proxy-addr"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: npm install -D @types/proxy-addr
Does proxy-addr@2.0.7 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("proxy-addr") from a CommonJS file and import "proxy-addr" from an ES module.
| Runtime | require("proxy-addr") | import "proxy-addr" |
|---|---|---|
| Node.js 18 | ✓ works | ✓ works |
| Node.js 20 | ✓ works | ✓ works |
| Node.js 22 | ✓ works | ✓ works |
| Node.js 24 | ✓ works | ✓ works |
| Node.js 26 | ✓ works | ✓ works |
| Bun 1.4.0 | ✓ works | ✓ works |
How to import proxy-addr
ES modules (import)
import proxyAddr from "proxy-addr";Named imports from a CommonJS package only work when Node.js can statically detect them. If a named import fails, use the default import and destructure.
CommonJS (require)
const proxyAddr = require("proxy-addr");Module format by version
Derived from the type, main and exports fields of every stable release on npm, corrected where a runtime test of that version contradicted them (27 versions; the newest 27 shown).
| Versions | Format | First published |
|---|---|---|
| 0.0.0 – 2.0.7 | CommonJS | May 5, 2014 |
Frequently asked
Is proxy-addr ESM-only?
proxy-addr@2.0.7 is a CommonJS package. proxy-addr ships CommonJS only. require("proxy-addr") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.10. import "proxy-addr" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.
Can I import proxy-addr with ES module syntax?
Yes. import proxyAddr from "proxy-addr" works in Node.js and Bun because they support importing CommonJS modules. Named imports work only when Node.js can statically detect the exports.
Does proxy-addr work in Bun?
Yes. import "proxy-addr" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does proxy-addr ship TypeScript types?
Not bundled. Install the community types with "npm install -D @types/proxy-addr".
Links
Other commonjs packages
- debug 4.4.3CommonJS
- semver 7.8.5CommonJS
- ms 2.1.3CommonJS
- picomatch 4.0.7CommonJS
- ajv 8.20.0CommonJS
- source-map 0.8.0CommonJS
- react-is 19.2.8CommonJS
- readable-stream 4.7.0CommonJS
Similar popularity
- arraybuffer.prototype.slice 1.0.4CommonJS
- @smithy/util-utf8 4.5.2CommonJS
- p-try 3.0.0ESM-only
- which-collection 1.0.2CommonJS
- @vitest/snapshot 5.0.0ESM-only
- istanbul-reports 3.2.0CommonJS
- json-stable-stringify-without-jsonify 1.0.1CommonJS
- @radix-ui/react-dismissable-layer 1.1.19Dual