TypeORM Paginator

Cursor-based pagination that works with TypeORM Query Builder. Read about the general idea of cursor-based pagination here.

This package is a fork of the typeorm-paginator package with some tweaks. See the Key differences from other packages section for more details.

The biggest difference is directional cursors. Directional cursors store the direction of pagination inside them. They allow to provide only one parameter to paginate in any direction.

• Installation
• Usage
  • With the Configuration step
    • Configuration
    • Retrieving pages
  • Without the configuration step
• Key differences from other packages
  • typeorm-paginator
  • typeorm-cursor-pagination
• Contributing
• Migration
  • v1 to v2
• License

Installation

1npm install typeorm-cursor-paginate --save

Usage

With the Configuration step

Start by importing the CursorPaginator class:

1import { CursorPaginator } from "typeorm-cursor-paginate";

Configuration

Instantiate the paginator with your target entity and define the ordering strategy. In this example, users are sorted by their name in ascending order and by id in descending order:

1const paginator = new CursorPaginator(User, {
2  orderBy: { name: "ASC", id: "DESC" },
3});

Prepare your query:

1const query = repoUsers.createQueryBuilder();
2// you can apply desired "where" conditions to the query

Retrieving pages

1. Retrieving the First Page

   Use the paginator to fetch the initial set of results. Here, a limit of 2 items per page is specified:

   1const firstPageResult = await paginator.paginate(query, { limit: 2 });

   Output structure:

   1{
   2  nodes: [
   3    User { id: 4, name: 'a' },
   4    User { id: 3, name: 'b' },
   5  ],
   6  hasPrevPage: false,
   7  hasNextPage: true,
   8  prevPageCursor: "some-cursor-string",
   9  nextPageCursor: "some-cursor-string",
   10}

2. Navigating to the Next Page

   To retrieve the next set of results, pass the nextPageCursor from the first query:

   1const secondPageResult = await paginator.paginate(query, {
   2  limit: 2,
   3  // Use the nextPageCursor from the previous result
   4  pageCursor: firstPageResult.nextPageCursor,
   5});

   Output structure:

   1{
   2  nodes: [
   3    User { id: 1, name: 'c' },
   4    User { id: 2, name: 'c' },
   5  ],
   6  hasPrevPage: true,
   7  hasNextPage: true,
   8  prevPageCursor: "some-cursor-string",
   9  nextPageCursor: "some-cursor-string",
   10}

Without the configuration step

There is also a way to skip the configuration step and use the paginate function directly. First, import the default from the package:

1import paginate from "typeorm-cursor-paginate";

Then, use it like this:

1// create a query builder
2const query = repoUsers.createQueryBuilder();
3// you can apply desired "where" conditions to the query
4
5// Get the first page
6const result = await paginate(User, query, {
7  orderBy: { name: "ASC", id: "DESC" },
8  limit: 2,
9});
10
11// Get the next page
12const resultNext = await paginate(User, query, {
13  orderBy: { name: "ASC", id: "DESC" },
14  limit: 2,
15  pageCursor: result.nextPageCursor,
16});

Key differences from other packages

typeorm-paginator

typeorm-paginator is the original package that this one is based on.

Here are the key differences:

• Directional cursors: In the original package, cursors are not directional. The pagination direction was determined by what argument the cursor is passed to. This package, on the other hand, stores the direction of pagination inside the cursor. It allows to provide only one parameter to paginate in any direction.
• Type safety: Added some more type safety to the code. Now the orderBy property only accepts keys that are present in the entity.
• Removed PageCursor: The PageCursor class was removed. This package is about cursor-based pagination.
• No default "limit": Original package had a default limit of 20. Now, if the limit is omitted, all results will be returned.

typeorm-cursor-pagination

typeorm-cursor-pagination is another package that provides cursor-based pagination for TypeORM. As of now, March 2025, it gets more and more popular than the typeorm-paginator package.

Here are the key differences:

• Ability to provide different directions for different columns in orderBy: In the typeorm-cursor-pagination package, all columns in the orderBy array had to have the same direction. This package, on the other hand, allows to provide different directions for different columns.
• Directional cursors: see above
• No default "limit": see above
• Custom transformation of the cursor: In the current package, custom transformers to stringify and parse the cursor can be provided. This feature comes from the original package (typeorm-paginator).

Contributing

All contributions are welcome, open a pull request or issue any time.

Please try to commit your changes using a descriptive commit message.

TODOs:

• make it work with all values allowed by TypeORM's FindOptionsOrderValue type for orderBy.
• properly setup eslint and prettier
• add to README example of using CursorTransformer
• rename CursorPaginatorParams.transformer to cursorTransformer

Migration

v1 to v2

• CursorPagination type was renamed to Paginated. Example: CursorPagination<User> became Paginated<User>.

License

Released under the MIT License