djs-core is a framework built on top of Discord.js that takes care of the repetitive scaffolding so you can focus on what your bot actually does.

Most Discord bots start the same way — you write a command handler, an event system, a file loader, and some boilerplate to wire everything together. You do this for every project. djs-core does it once, correctly, and gets out of your way.

File-based, not config-based. Drop a file in the right folder and it works. No registration, no imports, no index files to update. The structure of your project is the structure of your bot.

Typed by default. Command options are inferred directly from your builder chain — the options object in your handler is fully typed without any manual effort. Your editor knows what's there and what isn't.

Extensible, moving toward native features. Database (Drizzle) is now built into the core — client.db, db/ at the project root, and djs-core db CLI. Official plugins like @djs-core/plugin-drizzle are deprecated. Third-party plugins via definePlugin still work; we may eventually drop maintenance of official plugins as native equivalents land.

Built for the long run. djs-core includes a built-in linter (djs-core check) that catches deprecated patterns before they cause issues, and a scaffolding tool (djs-core generate) that creates files the right way every time.

• Slash commands, context menus, autocomplete
• Buttons, modals, all select menu variants
• Events and scheduled tasks (cron)
• Subcommand groups via folder structure
• Per-option typed autocomplete handlers
• Native Drizzle database — db: in config, interaction.client.db, migrations via djs-core db
• Plugin system with lifecycle hooks (third-party extensions)
• Static analysis with auto-fix

Deprecated official plugins (still in repo for migration, no longer recommended):

Long term, djs-core aims to ship common features (database, tooling, etc.) as core packages rather than optional official plugins. Community plugins using definePlugin are not affected.

// djs.config.ts
export default defineConfig({
  token: process.env.TOKEN!,
  servers: ["..."],
  db: { dialect: "sqlite" },
});

// in a command handler
import { Command } from "@djs-core/runtime";
import { eq, schema } from "@djs-core/db";

await interaction.client.db
  .select()
  .from(schema.todos)
  .where(eq(schema.todos.id, id));

Schema lives in db/schema.ts. CLI: djs-core db init | generate | migrate. Drizzle Kit config is synced from djs.config.ts — no duplicate dialect in drizzle.config.ts.

From the repository root:

bun install
bun dev

This builds workspace packages, starts their watch rebuilders, and runs the example bot in app/ via djs-core dev.

• Bot only: bun run dev:app (same as cd app && bun dev)
• Framework packages only: bun run dev:packages

Set TOKEN (and other env vars) in app/.env before starting the bot.

Full documentation is available at djs-core.cleboost.com.