Packages built quiet,
shipped in the open.
nodeproxy gives Node.js services a small, dependable layer for proxying and forwarding requests — built to drop into an existing server without dragging in a heavy framework.
$ Install it
Add the package to any Node.js project or install it globally with your package manager.
npm install -g @rexaray008/nodeproxy
Register your app
Tell nodeproxy how to run your application using pm2, so you don't need to start it manually.
nodeproxy app add myapp --cmd "npm start" --cwd /path/to/your/project
Point proxy route
Direct incoming proxy traffic (port 8080 by default) to your app's listening port.
nodeproxy add "*" http://localhost:3000
Setup public tunnel (Optional)
Connect a Cloudflare Tunnel to expose your local app on a live domain without opening ports.
nodeproxy tunnel setup --domain app.yourdomain.com --port 8080
Start everything
Boot your registered apps, proxy routing, and Cloudflare tunnel together in a single command.
nodeproxy start --tunnel
Every package, one growing shelf.
This grid is the whole point of the site: publish a package, drop it into data/packages.js, and a new card shows up here automatically.
A small tool, three common jobs.
Bridge internal services
Forward requests from a public-facing route to an internal service without exposing its address directly.
Sit in front of an API
Drop it in as a thin layer ahead of a third-party API — a place to add headers, logging, or retries later.
Mock during local dev
Point requests at a local stub while you build, then swap the target for the real endpoint at deploy time.
Ready when you are.
@rexaray008/nodeproxy is on the npm registry now — no account, no waitlist, just one install.
npm install @rexaray008/nodeproxyView on npm