npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

node-get-post-proxy

v0.0.2

Published

An http proxy - the first one who works with both GET and POST requests

Readme

#NodeGetPostProxy

When to use NodeGetPostProxy

You have a front-end application which always connect to an IP address and you have multiple server instances:

  • production: the higher percentage of users connect to it
  • development: you want to connect to it to test new features (but you cannot modify the frontend because it is mantained by another team)
  • staging: you want that a sample of the users connect to it in order to do an A/B testing

Your application has a login. You want to decide to which server a user connect basing on its username.

The solution with this module is to let the production server to act as a Proxy. If the user who does the request has to connect to the staging server, because its field "server" in the database is set to "staging", the production server does the request for him (with the get or post fields) and it will return the response.

The module automatically understand if the request was a GET or a POST and forward the GET or POST fields.

Installing NodeGetPostProxy

npm install nodegetpostproxy

How to use it

var express = require('express');
var app = express();
var http = require('http');
var httpProxy = require('NodeGetPostProxy');


var proxy = httpProxy.createProxyServer({
  target: "http://...." //link of the development server
});


app.use(function(req,res,next){
    if (req.params('user_name') == 'Pippo'){
      proxy.web(req,res);
    } else {
      return next();
    }
});

http.createServer(app).listen(80);
console.log('Listening on port 80...');

Run the example

You can find an example in the folder "example".

In 3 different terminal windows run:

  • node app.js
  • node app_development.js
  • node app_staging.js

Go to the browser:

With the link http://localhost will response the production server With the link http://localhost/?user_name=Pippo will response the development server With the link http://localhost/?user_name=Mario will response the staging server