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

@lightspeed/graphql-page-connection

v0.1.11

Published

Create relay connections from numbered pages pagination

Downloads

30

Readme

@lightspeed/graphql-page-connection

npm version

Introduction

Cursor pagination works by returning results after or before a pointer to an item in the dataset. We follow the Relay Cursor Connections Paginatinon Specification for pagination in GraphQL

Using an opaque string value as a cursor, we can abstract away the differences of underyling pagination schemes per endpoint, while giving us a consistent interface to consumers of the API.

This library provides an abstraction over the numbered pages pagination model, in which the data source is expecting a page number and a page size. The cursor is defined as base64('page:<page>;offset:<offset>').

Let's observe an example in which we request the first 4 items after cursor cGFnZTowO29mZnNldDoz, i.e.: base64('page:0;offset:3').

{
  "edges": [
    {
      "node": {
        "name": "banana"
      },
      "cursor": "cGFnZToxO29mZnNldDow" // base64('page:1;offset:0')
    },
    {
      "node": {
        "name": "apple"
      },
      "cursor": "cGFnZToxO29mZnNldDox" // base64('page:1;offset:1')
    },
    {
      "node": {
        "name": "pear"
      },
      "cursor": "cGFnZToxO29mZnNldDoy" // base64('page:1;offset:2')
    },
    {
      "node": {
        "name": "watermelon"
      },
      "cursor": "cGFnZToxO29mZnNldDoz" // base64('page:1;offset:3')
    }
  ],
  "pageInfo": {
    "hasNextPage": true,
    "hasPreviousPage": true,
    "startCursor": "cGFnZToxO29mZnNldDow", // base64('page:1;offset:0')
    "endCursor": "cGFnZToxO29mZnNldDoz" // base64('page:1;offset:3')
  },
  "totalCount": 45
}

From here, we have a few options:

  1. To paginate forward, we request the first 4 items after end cursor cGFnZToxO29mZnNldDoz, i.e.: base64('page:1;offset:3').
    • If we request the first 4 items after any other cursor, we'll receive an error. The numbered pages pagination model data source does not support this request.
  2. To paginate backwards, we request the last 4 items before start cursor cGFnZToxO29mZnNldDow, i.e.: base64('page:1;offset:0').
    • If we request the last 4 items before any other cursor, we'll receive an error. The numbered pages pagination model data source does not support this request.

Quick Start

  1. Install the dependency in your webapp.
yarn add @lightspeed/graphql-page-connection
  1. Implement your data fetching logic in the resolver.
import { pageFromConnectionArgs, connectionFromArray } from '@lightspeed/graphql-page-connection';

export const resolvers: ResolverMap = {
  Query: {
    products: async (_parent, { first, after, last, before }, { dataSources }) => {
      // Extract the page number and page size from cursor arguments
      const connectionArgs = { first, after, last, before };
      const { pageNum, pageSize } = pageFromConnectionArgs(connectionArgs);

      // Retrieve data and page metadata from data source
      const { productDataSource } = dataSources;
      const res = await productDataSource.getProducts({ pageNum, pageSize });
      const { data, pageCount, totalCount } = res;

      // Create a connection as an output
      const meta = { totalCount, pageCount };
      const connection = connectionFromArray(products, connectionArgs, meta);
      return connection;
    },
  },
};