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

paged-http-stream

v1.0.1

Published

Turn a paged http request into a stream of pages.

Downloads

9

Readme

paged-http-stream

Turn a paged http request into a stream of pages. Focuses on simplicity and modularity. Doesn't try to assume anything. You must implement a 'next' function that returns the next request based upon the previous one.

npm install paged-http-stream

API

var pages = pager(opts, next)

Options:

method: defaults to GET

uri: the url to query. includes query string.

... and anything else that can be passed to a typical node.js http request (uses got)

next = function (data)

You need to implement the next function, which be able to interpret the data from the previous request, passed in as an argument, into a new request.

Example

For example, figshare returns each of their search pages like this:

{
  "items_found" : 91,
  "page_nr": 1,
  "items": []
}

So, I can write a function next that takes the page_nr and adds one, and then returns null when the items list is empty:

function next (data) {
  // data will be JSON parsed already.
  if (data.error) throw new Error(data.error)
  if (data.items && data.items.length === 0) return null // we are done here
  var query = {
    search_for: 'this is my query',
    page: parseInt(data.page_nr + 1) || 1 // get the next page
  }
  return getOpts(query)
}

function getOpts (query) {
  return {
    method: 'GET',
    uri: 'http://api.figshare.com/v1/articles/search?' + qs.stringify(query)
  }
}

Then, pass to the pager:

var pageStream = pager(startingOpts, next)

You can then get access to each page like this (as JSON):

pageStream.on('data', funciton (page) {
  console.log(page.items)
})

As seen in

figshare-search

TODO

  • timeout, or wait time between requests