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

@hoursofza/djs-common

v1.5.0

Published

A common djs utility package

Downloads

125

Readme

djs-common

djs-common focuses on providing a simple framework for discord bots using discord.js. This includes a command handler, event handler, and a utility class for attaching reactions.

Features

  • Command Handler: Easily manage and organize your Discord bot commands.
  • Event Handler: Streamline the handling of Discord events with a simple event system.
  • Utilities: Various utility functions to simplify common tasks.

Installation

npm install djs-common

Handlers

Once a command and event directory is set up, the handlers will automatically load all commands and events. The command or event name should be the same as the file name. Invoking the command can be done as such:

client.on('message', (message) => {
  commandHandler.handleCommand(message);
});

Initializing all the events in the provided events directory can be done as such:

eventHandler.loadAllEvents((eventName, listener) => bot.on(eventName, listener));

Example Usage

The commandHandler class should be overridden as such:

class CommandHandlerLocal extends CommandHandler<Message> {
    constructor() {
        // method to check if the user is an admin, root of the project to the commands dir, local to commands dir
        super(isAdmin, `./${config.sourceDirPath}/commands`, '../commands');
    }

    requireModule(): NodeJS.Require {
        return require;
    }

    fsModule(): typeof import('fs') {
        return fs;
    }
}

const commandHandler = new CommandHandlerLocal();
export { commandHandler };

Invoke in the main file as such:

commandHandler.loadAllCommands();

The eventHandler class should be overridden as such:

class EventHandlerLocal extends EventHandler {
    constructor() {
        // root of the project to the events dir, local to events dir
        super(`./${config.sourceDirPath}/events`, '../events');
    }

    requireModule(): NodeJS.Require {
        return require;
    }

    fsModule(): typeof import('fs') {
        return fs;
    }
}
const eventHandler = new EventHandlerLocal();
export { eventHandler };

Invoke in the main file as such:

eventHandler.loadAllEvents((eventName, listener) => bot.on(eventName, listener));

Command/Event Files

Command and event classes should be created in the commands and events directory respectively.

myCommand.js

exports.run = async(message) => {
    // code here
}

myEvent.js

module.exports = async (eventObject) => {
    // code here
}

View usage here