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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@eliasrrosa/pagination

v0.0.11

Published

An framework-independent abstraction of the pagination functionality.

Readme

TS Pagination

A framework-independent pagination API. Easily implement pagination into any typescript/javascript project, regardless of it being front-end, back-end, React, Vue, Svelte, or another.

Installation

npm i @eliasrrosa/pagination@latest

Usage

Instantiate the pagination object. Pass it properties to modify its behavior. Then, use methods to access relevant data. Finally, move through pages.

import { Pagination } from "@eliasrrosa/pagination";

const pagination = new Pagination({
  take: 10,
  offset: 10,
  maximumPagesToDisplay: 3,
  totalItemsCount: 100,
});

console.log(pagination.getPages()); //output: [1,2,3];
console.log(pagination.getCurrentPage()); //output: 2;
console.log(pagination.getTotalQuantityOfPages()); //output: 10

pagination.goToNextPage();

console.log(pagination.getPages()); //output: [2,3,4];
console.log(pagination.getCurrentPage()); //output: 3;
console.log(pagination.getTotalQuantityOfPages()); //output: 10

pagination.goToPreviousPage();

console.log(pagination.getPages()); //output: [1,2,3];
console.log(pagination.getCurrentPage()); //output: 2;
console.log(pagination.getTotalQuantityOfPages()); //output: 10

In this example, Pagination will:

  1. Display take (10) items per page;
  2. Skip the first offset (10) items.
  3. Display at most maximumPagesToDisplay (3) pages at a time.

If immutability is necessary, like in React, you can navigate through pages immutably using:

import { Pagination } from "@eliasrrosa/pagination";

const pagination = new Pagination({
  take: 10,
  offset: 10,
  maximumPagesToDisplay: 3,
  totalItemsCount: 100,
});

console.log(pagination.getNextPage()) 
/* returns a new Pagination instance with properties as if it had navigated to the next page */

console.log(pagination.getPreviousPage()) 
/* returns a new Pagination instance with properties as if it had navigated to the previous page */

console.log(pagination.getPage(5));
/* returns a new Pagination instance with properties as if it had navigated to page 5 */

Default Behavior

  1. The current page will tend to be in the middle, meaning there will be a balance between pages displayed after the current page, and pages displayed before the current page.

  2. The number of pages after the current page will be greater than the number of pages before the current page when the maximum number of pages to be displayed is even.

  3. If there are enough pages to be displayed, the maximum number of pages to be displayed will always be equal to Pagination.maximumPagesToDisplay. Otherwise, as many pages as can be inferred by the properties received will be displayed.

Example implementations

  1. Check out this React implementation: https://codesandbox.io/p/sandbox/ts-pagination-4f6zdv

If you use another framework, or no framework, how would you implement it?