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-request

v2.0.2

Published

Simplified requests for paged (paginated) content.

Downloads

1,301,398

Readme

paged-request NPM version NPM monthly downloads NPM total downloads Linux Build Status

Simplified requests for paged (paginated) content.

Please consider following this project's author, Jon Schlinkert, and consider starring the project to show your :heart: and support.

Install

Install with npm:

$ npm install --save paged-request

Heads up!

See the release notes for information about changes made in v2.0.

Usage

This library recursively calls needle's .get method as long as the user-provided next() function returns a string (the next url to get). See an example.

Example

const request = require('paged-request');

request(url, options, next)
  .then(acc => console.log(acc.pages.length))
  .catch(console.error);

Params

  • url {string} - (required) the initial url to get
  • options {object} - (optional) options object to pass to needle
  • next {function} - (required) function that returns the next url to get, a promise or undefined.

next function params

  • url {string} - the original (base) user-provided url
  • resp {object} - needle response object
  • acc {object} - accumulator object with the following properties:
    • options {object} - user-provided options object
    • pages {array} - array of responses
    • urls {array} - array of requested urls

The next function should return a string (the next url to get), promise or undefined.

Example

The following example shows how to loop over pages of CSS posts on smashingmagazine.com (an arbitrary example, but they have great content!).

const request = require('paged-request');

async function next(url, resp, acc) {
  // do stuff to check response first if necessary
  const regex = /href="\/.*?\/(\d+)\/"/;
  const num = (regex.exec(resp.data) || [])[1];

  if (num && /^[0-9]+$/.test(num) && +num <= n) {
    // use the "original" url to avoid having to reparse
    // and recreate the url each time
    return `${acc.orig}/page/${num}/`;
  }
}

request('https://www.smashingmagazine.com/category/css', {}, next)
  .then(acc => console.log(acc.pages.length))
  .catch(console.error);

Release notes

v2.0

  • renamed .hrefs to .urls in response object
  • now using axios instead of needle. Please see the axios documentation for API information.

About

Pull requests and stars are always welcome. For bugs and feature requests, please create an issue.

Please read the contributing guide for advice on opening issues, pull requests, and coding standards.

Running and reviewing unit tests is a great way to get familiarized with a library and its API. You can install dependencies and run tests with the following command:

$ npm install && npm test

(This project's readme.md is generated by verb, please don't edit the readme directly. Any changes to the readme must be made in the .verb.md readme template.)

To generate the readme, run the following command:

$ npm install -g verbose/verb#dev verb-generate-readme && verb

Related projects

You might also be interested in these projects:

  • gists: Methods for working with the GitHub Gist API. Node.js/JavaScript | homepage
  • github-base: Low-level methods for working with the GitHub API in node.js/JavaScript. | homepage
  • repos: Tiny wrapper around github-base for getting publicly available information for a repository, or all of… more | homepage

Contributors

| Commits | Contributor |
| --- | --- |
| 12 | jonschlinkert |
| 9 | doowb |
| 2 | whitneyit |

Author

Jon Schlinkert

License

Copyright © 2021, Jon Schlinkert. Released under the MIT License.


This file was generated by verb-generate-readme, v0.8.0, on January 20, 2021.