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 🙏

© 2024 – Pkg Stats / Ryan Hefner

pull-http-client

v0.0.1

Published

make http client requests in pull streamy ways.

Downloads

8

Readme

pull-http-client

make http client requests in pull streamy ways.

api

http is a pretty ugly protocol. It has many features. pull-http-client starts with the most general interface to http for pull-streams, and then gives you several helpers that are each more suited to particular ways http is often used.

request(opts, cb(err, source)) => sink

The most basic format. returns a sink stream, and takes a callback which will be called with an error, and a source stream.

request.source(opts, cb (err)) => source

use for downloads. the source is the response.

request.sink(opts, cb(err, data)) => sink

use for uploads. the sink will pull your uploads to the server. data will contain the headers

request.duplex(opts, cb(err, data)) => duplex

You probably won't need this. If you seem to need this, you should probably use websockets instead. Some proxies will make this not work properly, but node<->node this should work.

request.async(opts, cb(err, data))

sometimes http is just a question and an answer. for smallish/fixed size responses don't use streams at all. just ask a question and get an answer.

License

MIT