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

djs-handler

v1.3.3

Published

Discord.js command handler

Readme

djs-handler

Discord.js command handler

npm bundle size npm GitHub issues GitHub pull requests NPM npm node-current

Example

for this file system:

commands directory
- command1.js
- command2.js
- command3.js
- command4.js
main file
shard file
package.json file
package-lock.json file
...

main file

const { Bot } = require('djs-handler'); // import module
const client = new Bot(/*your token here*/, { // constructor
    prefix: // your bot's prefix
    // you can add typing boolean to use typing for messages
    // you can add allowAllDM boolean to allow DM messages from everyone
    // you can ass DMWhitelist array with Discord user IDs to allow DM messages from specific users
    // you can add allowAllBot boolean to allow messages from all bot
    // you can ass BotWhitelist array with Discord user IDs to allow messages from specific bots
});
client.config(/*path of command files*/); // config all the files and login with the given token
// client.configDir is also available. See the references for more information.

command file

module.exports = {
    name: 'ping',
    aliases: ['latency'],
    run: async (client, message, args) => {
        message.channel.send(client.ws.ping);
    }
}

reload command file

module.exports = {
    name: 'reload',
    run: async (client, message, args) => {
        if (message.author.id != 'dev_id') return message.channel.send('You aren\'t a developer'); // replace 'dev_id' with your id.
        client.reload().then(x => message.channel.send(`reloaded ${x} commands`)).catch(() => message.channel.send('there was an error while reloading'));
    }
}

Tip: you can use Bot.configDir(dir) and Bot.reloadDir() for this file system:

commands directory
- category1
- - command1.js
- - command2.js
- category2
- - command3.js
- - command4.js
main file
shard file
package.json
package-lock.json
...

Bug report

Please use the issue tracker.

contributor

mswgen