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

http-connector

v0.1.2

Published

[![Build Status](https://travis-ci.org/edjafarov/http-connector.svg?branch=master)](https://travis-ci.org/edjafarov/http-connector) ## http-connector server to client and client to server connector

Readme

Build Status

http-connector server to client and client to server connector

Connector have two parts. The web part and server part. Connector allows not to think about how to implement communication between client and server and just send messages out and handle incoming messages. The connector abstracts communication to two methods (send and listen) on one side and two methods(send and listen) on other side. Implementations could vary and any protocol that can send messages will work. This specific implementation is for http.

Connector doesn't implement transaction. Thus to make the communication as a transaction it should be implemented on top of Connector.

You can also pass files through the connector to a server. You can build as complex message objects as you like and put objects anywhere, It could be multiple files in array for example . When the message will pass to a server the objects will have a stream property that you can use to pipe anywhere you like.

HTTPServerClientStream

var app = express();
app.use(bodyParser.json())
var sconn = connector.HTTPServerClientStream(app);
sconn.listen(function(message){
  //handle message
  message.files[0].stream.pipe(fs.createWriteStream())
  sconn.send({_response:message._response})
});
app.listen(process.env.PORT)

HTTPClientServerStream

var cconn = connector.HTTPClientServerStream();
cconn.send({files:document.getElementById('myInput').files})
cconn.listen(function(message){
  //handle response
});

IMPORTANT

If you want this to scale. You will need to make kind of sticky session. Because the files are posted outside of original request, thus this two requests should go to the same backend node.