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

@vouchington/pagination

v0.0.2

Published

Portable cursor codecs, guards, and configurable pagination query parsing.

Downloads

26,295

Readme

@vouchington/pagination

Portable opaque cursor codecs, cursor shape guards, and configuration-owned query parsing.

This package does not define resource identifiers, allowed filter values, public request limits, or response serialization. Those are application policy. It uses http-errors to report invalid client input as status 400 errors.

import { createPaginationParser, csvEnumFilter, enumFilter } from '@vouchington/pagination'

const parser = createPaginationParser({
  cursor: { paramName: 'after', legacyParamNames: ['cursor'] },
  limit: { paramName: 'limit', min: 1, max: 50, default: 20 },
  filters: {
    order: enumFilter('order', ['recent', 'popular'] as const),
    labels: csvEnumFilter('label', ['news', 'events'] as const),
  },
})

const options = parser.parse({ after: 'eyJpZCI6Ii4uLiJ9', limit: '10', order: 'recent' })

Use encodeCursor and decodeCursor for an opaque, canonical, unpadded base64url JSON envelope. Decoding rejects padding and the standard base64 + and / alphabet. Decode the result with one of the exported guards, or use a scoped decoder to validate a UUID key and prevent reuse across caller-defined scopes. buildPageInfo returns camelCase fields; applications choose their own wire format.