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

detritus-pagination

v1.4.0

Published

An easy to use pagination handler

Downloads

12

Readme

detritus-pagination

An easy-to-use paginator for the Discord API Wrapper Detritus.

Using CommandClient

By default, CommandClient#client returns a ClusterClient, which is a class that manages ShardClients. To make it work with detritus-pagination, either set useClusterClient to false in the CommandClient constructor, or use PaginatorCluster instead. It maintains a WeakMap<ShardClient, Paginator> internally.

Examples

// Imports
const { ShardClient } = require("detritus-client");
const { Paginator } = require("detritus-pagination");

// Detritus Client
const client = new ShardClient("token");

// Pagination Handler
const paginator = new Paginator(client, {
    // Maximum number of milliseconds for the bot to paginate
    // It is recommended not to set this too high
    // Defaults to 300000ms (5 minutes)
    maxTime: 300000,
    // Whether it should jump back to page 1 if the user tried to go past the last page
    // Defaults to false
    pageLoop: true,
    // Whether a page number should be shown in embed footers
    // If a string is passed as page, it will append the page number to the string
    pageNumber: true
});

// Reactions that will be passed in paginator.createReactionPaginator lateron
// This is optional and default emojis will be used if no `reactions` object is passed
const reactions = {
    previousPage: "⬅️",
    nextPage: "➡️"
};

const createEmbedMessage = (title, description) => ({
    embed: { title, description }
});

// Message event for commands 
client.on("messageCreate", async ctx => {
    const { message } = ctx;
    if (message.content === "!!test") {
        // Pages for this command
        const pages = [
            createEmbedMessage("Hello", ":)"),
            createEmbedMessage("Bye", ":(")
        ];

        // Create a ReactionPaginator
        const paging = await paginator.createReactionPaginator({
            // message is the message the user has sent
            message,
            // pages is an array of pages (will be passed as parameter in Message#edit)
            pages,
            // reactions is an object that includes `previousPage` and `nextPage` emojis (defined above)
            reactions
        });

        // You can also listen to events!
        // `next` event is fired when the user reacts with next page emoji
        // `previous` event is fired when the user reacts with previous page emoji
        paging.on("next", () => {
            message.reply("`next` event triggered");
        });

        paging.on("previous", () => {
            message.reply("`previous` event triggered");
        })

        paging.on("page", data => {
            message.reply(`skipped to page ${data.page}`);
        });
    }
});

// Run the client
(async () => {
    await client.run();
    console.log("Ready!");
})();