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

log-socket

v0.2.0

Published

tcp proxy socket that dumps everything through it to console.log - useful for debugging HTTP servers

Readme

log-socket

tcp proxy socket that dumps everything through it to console.log - useful for debugging HTTP servers

install

$ npm install log-socket

usage

var http = require('http')
var logsocket = require('logsocket')

var server = http.createServer(function(req, res){
	res.setHeader('x-test', 10)
	res.end('hello')
})

// redirect everything to this backend socket
var proxy = logsocket(8081, '127.0.0.1')

// Request data
proxy.on('input', function(chunk, enc){
	console.log(chunk.toString())	
})

// Response data
proxy.on('output', function(chunk, enc){
	console.log(chunk.toString())	
})

server.listen(8081)
proxy.listen(8080)

If you then curl to the logsocket - you will get a response from the backend HTTP server and the logsocket will dump all the traffic going through it

$ curl -L http://127.0.0.1:8080

api

var proxy = logsocket(port, [address, opts])

Return a tcp socket that will proxy traffic back to address:port - the default for address is '127.0.0.1'

Opts are passed into new net.Socket(opts)

events

proxy.on('input', function(chunk, enc){})

Called when data is recieved by the socket

proxy.on('output', function(chunk, enc){})

Called when data is sent by the socket

license

MIT