canirequire › ESM-only › http-proxy-middleware
Is http-proxy-middleware ESM-only? Can you require() it?
The one-liner node.js proxy middleware for connect, express, next.js and more
Last verified Sep 9, 2026 against http-proxy-middleware@4.2.0. Markdown · JSON
ESM-only ESM-only since 4.0.0 — last CommonJS version is 3.0.7
http-proxy-middleware dropped its CommonJS build in 4.0.0 (May 2026). The last version with a plain require()-able CommonJS entry is 3.0.7, published Jun 14, 2026; it declares support for Node.js ^14.18.0 || ^16.10.0 || >=18.0.0.
On Node.js 22.12+ and newer (http-proxy-middleware@4.2.0 declares Node.js ^22.15.0 || ^24.0.0 || >=26.0.0), require("http-proxy-middleware") works with the latest version: Node.js loads synchronous ES modules through require(). Verified on Node.js 22, 24 and 26. Node.js 18 has no require(esm), and http-proxy-middleware@4.2.0 declares Node.js ^22.15.0 || ^24.0.0 || >=26.0.0, so 18 is outside its supported range anyway.
http-proxy-middleware@4.2.0 declares engines "^22.15.0 || ^24.0.0 || >=26.0.0", so Node.js 18, 20 are outside its supported range regardless of module format.
What to do
- On Node.js 22.12+ and newer (http-proxy-middleware@4.2.0 declares Node.js ^22.15.0 || ^24.0.0 || >=26.0.0), require("http-proxy-middleware") works with the latest version: Node.js loads synchronous ES modules through require(). Verified on Node.js 22, 24 and 26.
- From a CommonJS file, use a dynamic import inside an async function: const httpProxyMiddleware = await import("http-proxy-middleware"). That works on every Node.js version the package supports (^22.15.0 || ^24.0.0 || >=26.0.0).
- If you need a synchronous require() or run Node.js 18: npm install http-proxy-middleware@3.0.7, the last CommonJS release (published Jun 14, 2026); it declares Node.js ^14.18.0 || ^16.10.0 || >=18.0.0.
- http-proxy-middleware@4.2.0 declares engines "^22.15.0 || ^24.0.0 || >=26.0.0", so Node.js 18, 20 are unsupported regardless: upgrade Node.js or pin an older release.
- TypeScript: types are bundled; install nothing extra.
Does http-proxy-middleware@4.2.0 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("http-proxy-middleware") from a CommonJS file and import "http-proxy-middleware" from an ES module.
| Runtime | require("http-proxy-middleware") | import "http-proxy-middleware" |
|---|---|---|
| Node.js 18 | ✗ failsERR_REQUIRE_ESM | ✗ failsSyntaxError |
| 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 http-proxy-middleware
ES modules (import)
import * as httpProxyMiddleware from "http-proxy-middleware";Namespace import shown because the ESM entry may have no default export; use named imports for what it exports.
CommonJS (require)
// Node.js 22.12+ and newer (verified):
const httpProxyMiddleware = require("http-proxy-middleware");
// Any Node.js version the package supports (^22.15.0 || ^24.0.0 || >=26.0.0), from an async function:
async function main() {
const httpProxyMiddleware = await import("http-proxy-middleware");
}
// Or pin the last CommonJS release (declares Node.js ^14.18.0 || ^16.10.0 || >=18.0.0):
// npm install http-proxy-middleware@3.0.7Module 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 (76 versions; the newest 60 shown).
| Versions | Format | First published |
|---|---|---|
| 4.0.0 – 4.2.0 | ESM-only | May 5, 2026 |
| 0.8.2 – 3.0.7 | CommonJS | Sep 23, 2015 |
Frequently asked
Is http-proxy-middleware ESM-only?
http-proxy-middleware@4.2.0 is ESM-only. http-proxy-middleware dropped its CommonJS build in 4.0.0 (May 2026). The last version with a plain require()-able CommonJS entry is 3.0.7, published Jun 14, 2026; it declares support for Node.js ^14.18.0 || ^16.10.0 || >=18.0.0.
Which version of http-proxy-middleware still supports CommonJS / require()?
3.0.7 is the last version of http-proxy-middleware with a CommonJS build; it declares Node.js ^14.18.0 || ^16.10.0 || >=18.0.0. Install it with "npm install http-proxy-middleware@3.0.7". Every version from 4.0.0 on is ESM-only.
How do I use http-proxy-middleware from a CommonJS file?
From a CommonJS file, use a dynamic import inside an async function: const httpProxyMiddleware = await import("http-proxy-middleware"). That works on every Node.js version the package supports (^22.15.0 || ^24.0.0 || >=26.0.0). On Node.js 22.12+ and newer (http-proxy-middleware@4.2.0 declares Node.js ^22.15.0 || ^24.0.0 || >=26.0.0), require("http-proxy-middleware") works with the latest version: Node.js loads synchronous ES modules through require(). Verified on Node.js 22, 24 and 26. Alternatively pin http-proxy-middleware@3.0.7 (declares Node.js ^14.18.0 || ^16.10.0 || >=18.0.0).
Does http-proxy-middleware work in Bun?
Yes. import "http-proxy-middleware" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does http-proxy-middleware ship TypeScript types?
Yes. http-proxy-middleware bundles its own type declarations; no @types package is needed.
Links
Other esm-only packages
- ansi-styles 7.0.0last CJS
5.2.0 - strip-ansi 7.2.0last CJS
6.0.1 - commander 15.0.0last CJS
14.0.3 - supports-color 11.0.0last CJS
8.1.1 - chalk 6.0.0last CJS
4.1.2 - string-width 8.2.2last CJS
4.2.3 - ansi-regex 6.3.0last CJS
5.0.1 - escape-string-regexp 5.0.0last CJS
4.0.0
Similar popularity
- colors 1.4.0CommonJS
- @smithy/querystring-parser 4.5.2CommonJS
- validator 13.15.35CommonJS
- make-fetch-happen 16.0.1CommonJS
- cross-env 10.1.0ESM-only
- query-string 9.5.1ESM-only
- nodemailer 10.0.1Dual
- redux-thunk 3.1.0Dual