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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@harmonixjs/core

v2.0.1

Published

A modern TypeScript-only Discord.js framework with decorators, database integration, and advanced handlers

Readme

🤖 Harmonix Framework

npm version TypeScript License: MIT

A modern, type-safe Discord.js framework with decorators and advanced features.

Typed decorators without repeated generics

Decorated classes are the primary HarmonixJS API. Create a typed decorator definition once, then reuse it for the class and its inferred handler:

const GuildCreated = Event(Events.GuildCreate);

@GuildCreated
export default class GuildCreatedEvent {
  execute = GuildCreated.handler(async (bot, guild) => {
    // guild is inferred as Guild
  });
}

const Ping = Command({
  name: "ping",
  description: "Ping",
  type: "prefix"
});

@Ping
export default class PingCommand {
  execute = Ping.handler(async (bot, ctx) => {
    // ctx is inferred as CommandContext<"prefix">
  });
}

No implements EventExecutor<...> or implements CommandExecutor<...> is required. The defineEvent, defineCommand, and defineComponent helpers remain available as a secondary functional API.

Application events are declared once through module augmentation:

declare module "@harmonixjs/core" {
  interface HarmonixCustomEvents {
    "guild:configured": [guildId: string, enabled: boolean];
  }
}

bot.events.on("guild:configured", (bot, guildId, enabled) => {
  // bot is always injected as the first argument
});

await bot.events.emitAsync("guild:configured", guild.id, true);

Providers use the same typed registry pattern:

declare module "@harmonixjs/core" {
  interface HarmonixProviderRegistry {
    notifications: NotificationProvider;
  }
}

const bot = new Harmonix({
  // ...
  providers: [new NotificationProvider()]
});

bot.providers.notifications.send();

⚠️ TypeScript Only - JavaScript is not supported.

✨ Features

  • 🎯 TypeScript-first with full type safety
  • 🎨 Decorator-based commands and events
  • 📥 Automatic imports so you write less and code faster
  • 🔌 Plugin system for extensibility
  • 🚀 Easy to use with minimal setup

📦 Installation

npm install @harmonixjs/core tsx discord.js
npm install --save-dev typescript

🚀 Quick Start

1. Initialize TypeScript

npx tsc --init

Update tsconfig.json:

{
  "compilerOptions": {
    "target": "ESNext",
    "module": "ESNext",
    "moduleResolution": "node",
    "experimentalDecorators": true,
    "emitDecoratorMetadata": true,
    "outDir": "dist",
    "esModuleInterop": true
  }
}

2. Create your bot

// src/index.ts
import { Harmonix } from "@harmonixjs/core";
import { DatabasePlugin } from "@harmonixjs/quick-db";

interface User {
  id: string;
  coins: number;
}

const bot = new Harmonix({
  bot: {
    id: "YOUR_BOT_CLIENT_ID",
    token: "YOUR_BOT_TOKEN"
  },
  publicApp: true,
  folders: {
    commands: "./src/commands",
    events: "./src/events",
    components: "./src/components"
  },
  plugins: [
    new DatabasePlugin()
  ],
  intents: [3249151] // (All Intents)
});

// The plugin name and type are inferred automatically.
const users = bot.plugins.database.table<User>("users");

// Start listening
bot.start();

3. Create a command / event / component

// src/commands/Ping.ts
const Ping = Command({
  name: "ping",
  description: "Ping command"
});

@Ping
export default class PingCommand {
  execute = Ping.handler(async (bot, ctx) => {
    await ctx.reply(`Pong! ${bot.ws.ping}ms`);
  });
}
// src/events/Ready.ts
const Ready = Event(Events.ClientReady);

@Ready
export default class ClientReady {
  execute = Ready.handler((bot, client) => {
    bot.logger.sendLog("SUCCESS", `Bot is ready! Logged in as ${client.user.tag}`);
  });
}
// src/components/TestButton.ts
const TestButton = Component({ id: "test_button" });

@TestButton
export default class TestButtonComponent {
  execute = TestButton.handler(async (bot, ctx) => {
    await ctx.reply("Test button clicked!");
  });
}

4. Run your bot

npx tsx src/index.ts

📚 Documentation

🔌 Plugins

Harmonix supports first-class plugins — you can add plugins directly to the framework to register commands, events, middleware, or extend internals.

Official and third-party plugins can augment the typed registry:

export class MyPlugin implements HarmonixPlugin {
  readonly name = "myPlugin" as const;

  init(bot: Harmonix) {
    // Initialize the plugin.
  }
}

declare module "@harmonixjs/core" {
  interface HarmonixPluginRegistry {
    myPlugin: MyPlugin;
  }
}

Applications can then use bot.plugins.myPlugin without a generic, optional chaining, or a non-null assertion. Accessing a plugin that was not registered throws an explicit runtime error.

Application command capabilities

Harmonix forwards Discord.js application-command options directly:

import {
  ApplicationCommandOptionType,
  ApplicationCommandType,
  ApplicationIntegrationType,
  InteractionContextType
} from "discord.js";

@Command({
  name: "profile",
  description: "Display a profile",
  contexts: [
    InteractionContextType.Guild,
    InteractionContextType.BotDM,
    InteractionContextType.PrivateChannel
  ],
  integrationTypes: [
    ApplicationIntegrationType.GuildInstall,
    ApplicationIntegrationType.UserInstall
  ],
  options: [{
    name: "user",
    description: "The user to display",
    type: ApplicationCommandOptionType.User
  }]
})

User and message context commands are also supported:

@Command({
  name: "View profile",
  type: "user",
  applicationType: ApplicationCommandType.User
})
  • @harmonixjs/quick-db: Simple and flexible Quick.db plugin for Harmonix Discord framework.
  • @harmonixjs/express: A powerful Express-based HTTP API plugin for the Harmonix Discord framework.
  • @harmonixjs/i18n: Runtime translations and Discord command localization.
  • @harmonixjs/shard: Automatic multi-process sharding using Discord's recommended shard count.
  • @harmonixjs/image-builder: Development..