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

discordselfbot

v0.0.2

Published

my own discord selfbot

Downloads

2

Readme

discord-selfbot

How to run

  1. Clone the repo or use npm

$ git clone https://github.com/megadrive/discord-selfbot

$ npm install discordselfbot

  1. Install dependencies

$ npm install

  1. Create a config file by making a copy of config.json.example and renamed it to config.json. If you want to use the weather command, you must obtain both a Google Maps Geocoding API key and a Dark Sky API key. Without these weather will emit a warning on use.

  2. Run the bot!

$ npm start

Creating your own commands

As of writing, a command has three exports. An object on the exports variable itself, a help function and a run function. Always include 'use strict' to avoid complications.

exports should contain an object with an aliases array and event which is a string.

aliases is an array of anything that you want this to fire from. So, given the default prefix of _, calling _triggers, _to_ or _fire will cause this command to run. One caveat is that if you double-up on command triggers, the later loaded will overwrite the older. Generally speaking, if your command file starts with 'a' and your 'z' function has a trigger of 'a', calling _a will run the command 'z'.

event is a string that you will nearly definitely not need to change. If you do, you will need to create a new bot.on() function in app.js. Open an issue if you need it.

module.exports = {
  aliases: ['triggers', 'to', 'fire'],
  event: 'message'
}

This next block is the help function that is used when calling a function with the --help flag. usage is an array, add another if your command has more than one usage. See replace.js for an example.

module.exports.help = function () {
  let conf = require('../config')
  return {
    description: `Your command's description.`,
    usage: [`${conf.prefix}${module.exports.aliases[0]} your usage information.`]
  }
}

This is the crux of your command. Do whatever you need to here.

module.exports.run = function (message) {
	// your code to enact here
}

Full example:

'use strict'

module.exports = {
  aliases: ['triggers', 'to', 'fire'],
  event: 'message'
}

module.exports.help = function () {
  let conf = require('../config')
  return {
    description: `Your command's description.`,
    usage: [`${conf.prefix}${module.exports.aliases[0]} your usage information.`]
  }
}

module.exports.run = function (message) {
	// your code to enact here
}