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

@chenshunyu/proxy

v1.0.0-beta.43

Published

`@chenshunyu/proxy` is a lightweight HTTP proxy server designed to help developers easily modify HTTP request headers for testing and debugging network requests.

Readme

@chenshunyu/proxy is a lightweight HTTP proxy server designed to help developers easily modify HTTP request headers for testing and debugging network requests.

Installation

Install @chenshunyu/proxy via npm:

npm i @chenshunyu/proxy

Usage

Start the proxy server:

node node_modules/@chenshunyu/proxy --port 8080 --file headers.txt

Parameters

  • --port: Specifies the port number the proxy server listens on. Default is 8080.

  • --file: Specifies the path to the file containing request header information. The file format should be key-value pairs, one per line, for example:

GET /example/path HTTP/1.1
key1: value1
key2: value2

Getting the Request Header File

  1. Open the browser developer tools (usually by pressing F12 or right-clicking and selecting "Inspect").
  2. Go to the "Network" tab.
  3. Right-click any request and select "Copy" -> "Copy request headers". help
  4. Paste the copied content into a text file and save it as headers.txt.

Request Expiration

When a request expires, you can continue using the proxy service by updating the headers.txt file.

Usage Security Recommendation

For security purposes, it's strongly recommended to add headers.txt to your .gitignore/.npmignore files. This prevents accidental exposure of sensitive headers (like cookies or tokens) in version control systems.

Example .gitignore entry:

+ # Ignore proxy header files
+ headers.txt

Example

Assume you have a file named headers.txt with the following content:

GET /example/path HTTP/1.1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.121 Safari/537.36
Accept-Language: en-US,en;q=0.9
Cookie: session=abc123; user=JohnDoe
Host: example.com
Referer: https://example.com/login
X-CSRF-TOKEN: abcdef123456

Start the proxy server:

node node_modules/@chenshunyu/proxy --port 8080 --file headers.txt

Now, the proxy server will run on port 8080 and use the request header information from the headers.txt file. If the request expires, update the headers.txt file.