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

@aleclarson/quest

v0.9.0

Published

Isomorphic HTTP client

Readme

quest v0.9.0

Bare bones HTTP requests for browser and server.

quest(method, url, headers)

Send any request, and return the request stream immediately.

const req = quest('POST', 'http://your-api.com/users/1')
req.on('response', (res) => {
  if (res.statusCode != 201) {
    console.warn('Failed to create user!')
  }
})
req.write(JSON.stringify({id: 'aleclarson', age: 23}))
req.end()

quest.stream(url, headers)

Send a GET request, and return the response stream immediately.

const res = quest.stream('https://stream.twitter.com/1.1')
res.on('data', console.log)
res.on('error', (error) => {
  error.args // => ['https://stream.twitter.com/1.1']
  error.req // => The request stream
  error.res // => The response stream
})

quest.fetch(url, headers)

Send a GET request, then buffer the entire response into memory.

const buffer = await quest.fetch('https://loripsum.net/api')
Buffer.isBuffer(buffer) // => true

quest.json(url, headers)

Send a GET request, then parse the response as JSON.

const json = await quest.json('https://your-api.com')
if (json == null) {
  console.log('The response was empty')
}

Tips and tricks

In NodeJS, the stream, fetch, and json functions all accept a ClientRequest object (the same object type that quest() returns). This means you can easily avoid lots of boilerplate code for non-GET requests.

const req = quest('PUT', 'https://localhost:8000', headers)
req.write(json)

// Convert the ClientRequest into a response object.
quest.stream(req)
  .on('data', (data) => {})
  .on('error', (err) => {})

// Convert the ClientRequest into a Buffer promise.
quest.fetch(req).then(buffer => {})

// Convert the ClientRequest into a JSON promise.
quest.json(req).then(data => {})

Caveats

  • The stream function can only be used in NodeJS (for now)
  • The request object returned by quest() cannot be passed to the other functions in the web version (yet)