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 🙏

© 2025 – Pkg Stats / Ryan Hefner

http-bypass

v1.2.0

Published

Bypass your HTTP/HTTPS backend service configrablly in an easy way

Readme

node-http-bypass

Bypass your HTTP/HTTPS backend service configrablly in an easy way.

Usecase

We use this tool to develop our new forum project without any changes on server-side, which is based on the discourse API, the CORS-required website.

CORS sometimes take you in a trap, and block your development flow, Yep? With node-http-bypass, you could customize anything that you wanna without changes on your server-side, just start writing code and put the CORS configurations after the demo is ready for production!

Your usecase? create Pull Request to submit :p

Usage

You need to define the following JSON under your working directory:

{
  "listen": 8888,
  "targetURL": "https://github.com",
  "outgoing": {
    "access-control-allow-headers": "+Content-Type"
  }
}

This JSON should be named as .bypassconfig and under your CWD. Run bypass or http-bypass in your shell, the program reads this config file, and do the followings:

  • start the proxy server on listen as its port.
  • when requesting to proxy server, it do request based on the targetURL.
  • when the target responds to proxy server finally, it rewrites the headers by the field outgoing.
    • for the +s rule, it inserts the given string to the header.
    • for the s(string) rule, it replaces the whole value of the specific header.

Wanna an API to integrate?

Yes, it also provides programming interface for doing what you want. Just like the following:

const ByPassServer = require('http-bypass').ByPassServer
const proxy = new ByPassServer({
  listen: 8000,
  targetURL: 'https://github.com',
  outgoing: {},
})
proxy.start()

The config object structure follows the .bypassconfig, so just see Usage for details.

Installation

$ npm i node-http-bypass -g

License

MIT @ Rokid, Inc.