chimurai/http-proxy-middleware

★ 11,124TypeScriptAudience · developerComplexity · 2/5LicenseSetup · easy

Mindmap

mindmap
  root((repo))
    What it does
      HTTP request forwarding
      CORS workaround
      Path rewriting
      WebSocket proxy
    Tech stack
      TypeScript
      Node.js
      Express
      httpxy
    Features
      Path filtering
      Request interception
      Plugin system
    Frameworks
      Express
      Next.js
      Connect
      Hono

mindmap root((repo)) What it does HTTP request forwarding CORS workaround Path rewriting WebSocket proxy Tech stack TypeScript Node.js Express httpxy Features Path filtering Request interception Plugin system Frameworks Express Next.js Connect Hono

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Route API calls from a React or Next.js frontend through a local proxy to avoid browser CORS errors during development.

USE CASE 2

Rewrite URL paths before forwarding, map /api/v1 on your server to a different path on the target service.

USE CASE 3

Forward WebSocket connections through the same proxy middleware alongside regular HTTP requests.

USE CASE 4

Bundle reusable proxy configuration as a named plugin to apply consistent routing across multiple server setups.

Tech stack

TypeScriptNode.jsExpressNext.js

Getting it running

Difficulty · easy Time to first run · 5min

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

In plain English

http-proxy-middleware is a Node.js library that lets you forward incoming HTTP requests from your server to a different server. This is commonly needed when building web applications where the frontend and backend run on separate addresses, and you want the frontend to be able to make requests without hitting browser security restrictions that block cross-origin requests. The library is designed to work as middleware, meaning you plug it into an existing server framework rather than running it standalone. It works with popular Node.js server tools including Express, Connect, Next.js, and Hono, among others. Setting it up is typically a single function call where you specify the destination server address. Once configured, incoming requests that match a path you specify get forwarded to the target server. The library gives you options to filter which requests get proxied using path strings, wildcard patterns, or a custom function. You can also rewrite the URL path before forwarding, so for example a request coming in at /api/users could be sent to /v2/users on the target server. For more advanced use cases, the library allows you to intercept and modify both requests before they are forwarded and responses before they are returned to the original caller. It also supports WebSocket connections, not just regular HTTP. A plugin system lets you bundle reusable configuration as named plugins. The package is available on npm and the source code is written in TypeScript, so type definitions are included. It relies on an underlying proxy library called httpxy, which is a maintained fork of the older http-proxy package. The project has a test suite and documentation with working examples for common scenarios. It is released under the MIT License.

Copy-paste prompts

Prompt 1

I have an Express server and a separate API server on a different port. Show me how to configure http-proxy-middleware to forward /api requests to the API server and avoid CORS errors.

Prompt 2

I need to rewrite the URL path before proxying, requests at /api/users should be forwarded as /v2/users on the target. How do I configure pathRewrite for this?

Prompt 3

How do I intercept and modify the response body before it is returned to the client using http-proxy-middleware's response interceptor?

Prompt 4

Show me how to add http-proxy-middleware to a Next.js app so API requests from the browser are proxied to a separate backend service.

Open on GitHub → Explain another repo

← chimurai on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.