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 🙏

© 2024 – Pkg Stats / Ryan Hefner

normalize-proxy

v1.0.4

Published

Install, normalize, then SPDY Push repositories

Downloads

25

Readme

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://github.com/normalize/proxy.js
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://github.com/normalize/proxy.js
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.

Platform

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.