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

@the-expanse-discord/protomolecule

v3.1.8

Published

General purpose bot for The Expanse Discord server.

Downloads

3

Readme

Protomolecule

build

dependencies Status devDependencies Status

General purpose bot for The Expanse Discord server.

Running locally

Put the following in a file named config.json5:

{
	"token": "<bot token>",
	"owner": "<owner discord id>",
	"commandPrefix": ".",
	"statusType": "WATCHING",
	"statusText": "you sleep...",
	"unlimitedRoles": [ "The Rocinante", "Moderation Team" ],
	// Lists which channels to respond to commands in. Use "all" in the list to respond in all visible channels.
	"commandChannels": ["all"],
	// A map from servers to reaction channels
	"welcomeChannels": {
        "{SERVER_ID}": "{CHANNEL_ID}",
    }
}

Use npx to run the bot: npx @johndaniels/protomolecule config.json

Or install the command and run it:

npm install -g @johndaniels/protomolecule

protomolecule cconfig.json5

Developer Setup

Copy the example config files over to a usable config.

cp .\config.example.json5 config.json5

Update Configs

View the files and identify the values that you need to supply.

npm install npm run dev

  • Edit config.json with the appropriate values.
    • token - Discord bot token.
    • owner - The Discord ID of the bot owner.
    • commandPrefix - Specify the command prefix.
    • statusType - What status is the bot?
    • statusText - Accompanying text for the bot status.
    • unlimitedRoles - Names of roles that aren't affected by rate limiting.
    • commandChannels - Lists which channels to respond to commands in. Use "all" in the list to respond in all visible channels.
    • welcomeChannels - A mapping of guild IDs to welcome channels. Protomolecule will use these to automatically create a welcome message and messages to react to.

After running these, you will also need to set up any guilds in welcomeChannels with the appropriate emoji and roles.

You can set up emoji with appropriate images and names matching those in the Emoji.ts file under src/Infrastructure/Enums/Role Assignment. You'll also have to set up roles with the same names (although spaces are allowed in the roles).

Lint

npm run code:lint

Correct any lint errors you might have.

Build

npm run code:build

Run Development Build

npm run dev

Debugging

Run the VSCode launch task to spin up a temporary instance for debugging.