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

butter-proxy

v2.0.1

Published

Passes incoming requests to locally running development servers

Downloads

9

Readme

butter-proxy

npm

$ npm install -g butter-proxy
$ butter-proxy

Uses netstat to automatically find running servers and then passes requests to hosts matching the folder name of the server to the correct port.

For instance, a request to www.resume.pxy would be passed to port 3000 assuming a process in ~/src/resume/www is listening on port 3000.

Example

  1. butter-proxy is installed and run on port 8080
  2. A server is started on port 5050 in ~/src/some-thing
  3. butter-proxy sees the server automatically and informs us
  4. A request is made with a host matching the directory, some-thing.pxy
  5. butter-proxy passes the request to port 5050
  6. The server on port 5050 is taken offline with a handy ^C
  7. butter-proxy promptly informs us the host name is no longer active

Options

  • Change the port with butter-proxy -p 8080
  • Change the base directory (what isn't included in the domain) with butter-proxy -b ~/code. By default this is ~/src
  • Change the TLD with butter-proxy -t dev. By default this is pxy