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

rampage

v0.1.0

Published

A generic way to split an array into pages, with optional callbacks to modify the structure of each page.

Downloads

5

Readme

Rampage.js npm Version Build Status Coverage Status

A generic way to split an array into pages, with optional callbacks to modify the structure of each page.

API

rampage(arr, numPerPage [, opts])

var arr = [
  { foo: 'bar' },
  { foo: 'baz' },
  { foo: 'qux' }
];

rampage(arr, 2);
/* [
 *   [ arr[0], arr[1] ],
 *   [ arr[2] ]
 * ]
 */

Pass in opts if you want to create previous/next links or customise the structure of each page:

var opts = {
  preProcess: function(pageItems, pageNum, totalPages) {
    return {
      pageItems: pageItems,
      pageNum: pageNum
    };
  },
  postProcess: function(currPage, prevPage, nextPage, pageNum, totalPages) {
    currPage.prevPage = prevPage;
    currPage.nextPage = nextPage;
    return currPage;
  }
};

var result = rampage(arr, 2, opts);
/* [
 *   {
 *     pageItems: [ arr[0], arr[1] ],
 *     pageNum: 0,
 *     prevPage: undefined,
 *     nextPage: result[1]
 *   },
 *   {
 *     pageItems: [ arr[2] ],
 *     pageNum: 1,
 *     prevPage: result[0],
 *     nextPage: undefined
 *   }
 * ]
 */

The opts.preProcess function maps over each slice of arr. It takes the following arguments:

  1. pageItems — The current slice of arr, which would have at most numPerPage number of items.
  2. pageNum — The current page number. Page numbers start from 0.
  3. totalPages — The total number of pages.

The opts.postProcess function maps over the result of opts.preProcess. It takes the following arguments:

  1. currPage — The current page.
  2. prevPage — A reference to the previous page, or undefined if there is no previous page.
  3. nextPage — A reference to the next page, or undefined if there is no next page.
  4. pageNum — The current page number. Page numbers start from 0.
  5. totalPages — The total number of pages.

Installation

Install via npm:

$ npm i --save rampage

Changelog

  • 0.1.0
    • Initial release

License

MIT license