Install, normalize, then SPDY Push repositories
Last updated 4 years ago by jongleberry .
MIT · Repository · Bugs · Original npm · Tarball
$ cnpm install normalize-proxy 
SYNC missed versions from official npm registry.

Normalize Proxy

NPM version build status Test coverage Gittip

Install a remote repository locally to be served via SPDY Push.

Setting Up

You'll notice a Dockerfile located at the root of this repository. With docker, you should be able to go through the following steps to run the proxy (not yet tested as of v0.1.0):

git clone git://
cd proxy.js
vim Dockerfile # change all the environmental variables
# maybe add your own .npmrc file
sudo docker build -t myname/normalize-proxy .
docker run -p 8080:8080 -d myname/normalize-proxy

If this doesn't work, please let me know!

If you're on a UNIX platform, you don't need to use Docker! Just look at the Dockerfile and set the same environmental variable. After that, running npm start should work:

git clone git://
cd proxy.js
npm i
export PORT=8888
npm start

Private Repositories

To access private repositories, you must either add authentication environmental variables or add files.

  • GitHub - set the NORMALIZE_AUTH_GITHUB env var for basic auth. It should be of the form <username>:<token>. You should use GitHub OAuth Tokens.
  • NPM - having a .npmrc file should be sufficient. For docker, you should add it to the image. This is untested - please let me know if it works.


This server is designed to run on UNIX systems and is thus able to avoid many issues and code bloat. Since this proxy is not designed to be run on clients, there's no need to support Windows. However, a Dockerfile will be included to make it easy for you to setup a proxy in a VM.

Today 0
This Week 0
This Month 0
Last Day 0
Last Week 0
Last Month 40
Dev Dependencies (10)
Dependents (0)

Copyright 2014 - 2016 © |