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

trans-log-proxy

v0.0.1

Published

HTTP transparent logging proxy

Readme

trans-log-proxy

HTTP transparent logging proxy

If you want to log headers and body of request and response for some micro-service in your system then you can set DEFAULT_URL equal to micro-service address and replace its url in config files with address of this proxy - after this headers/body of request/response logs to console.

Usually I run it as a service with pm2sd and get log files at /var/log, but you can look through console output.

Config

| Name | Description | | -------- | ------- | |PORT|Listening port| |DEFAULT_URL|All requests will be forwarded to this url| |ADDITIONAL_URL_COUNT|You can add several exceptions (and this is its' quantity):| |ADDITIONAL_{N}PATH|Requests with url starting with given path will be redirected to url specified below| |ADDITIONAL{N}_URL|('N' means number; starting from 1)|

Run

node index.js config.file

(you can omit config.file and it will use ./index.cfg)

Sample output

Using config from C:\Users\A\src\_github\cfg
  all --> http://192.168.1.1/
Server listening at http://localhost:8081

>> POST htpp://192.168.1.1:80/realms/myrealm/protocol/openid-connect/token
>> HEADERS
   content-type = application/x-www-form-urlencoded
   content-length = 51
   connection = close
>> BODY[51]  grant_type=password&client_id=myclient&scope=openid
<< 401
<< HEADERS
   server = nginx/1.24.0 (Ubuntu)
   date = Sun, 19 Oct 2025 23:40:37 GMT
   content-type = application/json; charset=utf-8
   content-length = 77
   connection = close
   cache-control = no-store
   pragma = no-cache
   referrer-policy = no-referrer
   strict-transport-security = max-age=31536000; includeSubDomains
   x-content-type-options = nosniff
   x-frame-options = SAMEORIGIN
<< BODY[77] {"error":"invalid_request","error_description":"Missing parameter: username"}