# discord.js: the Node.js wrapper for the Discord API, and where it stops fitting > discord.js is a TypeScript library that turns the Discord API into a Node.js client, shipped as a monorepo of focused packages. It is the default choice for JavaScript bot work and a poor fit for anyone who wants a thin, dependency-light HTTP layer. **discordjs/discord.js** — A powerful JavaScript library for interacting with the Discord API - Repository: https://github.com/discordjs/discord.js - Website: https://discord.js.org - Stars: 26,821 · Forks: 4,069 - Language: TypeScript - License: Apache-2.0 - Published: 2026-09-21 · Updated: 2026-09-21 · Language: en - Canonical page: https://hysenlabs.com/projects/discordjs-discord-js ## What problem discord.js solves, and who it is aimed at The Discord API is not one interface. A bot has to hold a persistent gateway connection, receive events over it, and separately issue REST calls to send messages, register slash commands and edit channel state. Doing that by hand means writing a reconnect loop, a rate-limit aware HTTP client and a cache before you write a single command. discord.js exists to remove that work: the README describes the main package as a Node.js module that "allows you to easily interact with the Discord API". The intended reader is a JavaScript or TypeScript developer building a bot. The repository's keywords are discord, api, bot, client, node and discordapp, and the topics list adds bot, discord-bot and voice-support. That is a narrow audience, and the project does not pretend otherwise. If you are building a web dashboard that reads a couple of guild endpoints, you are paying for a gateway stack you will never open. ## The monorepo layout: discord.js is the assembled wrapper, not the whole story The repository is a pnpm workspace. package.json sets "private": true and version 0.0.0, and the build, test and lint scripts all delegate to turbo run, so nothing is built at the root. The README states plainly that the repository "contains multiple packages with separate releases" and that the assembled wrapper lives under packages/discord.js. That matters when you debug. The layers are split: @discordjs/ws wraps the gateway, @discordjs/rest talks to the REST API, @discordjs/builders constructs API payloads, @discordjs/voice handles the voice API, and @discordjs/core is described as a thinly abstracted wrapper around the core components of the Discord API. @discordjs/collection and @discordjs/util are general utilities. There is also a create-discord-bot CLI for scaffolding, and a discordjs/proxy container described as a lightweight HTTP proxy for Discord's API. The practical consequence is that a bug in reconnection behaviour belongs to @discordjs/ws, not to the package you imported, and the releases are versioned independently. @discordjs/rest@2.6.3 shipped on 2026-07-19, four days after 14.27.0 on 2026-07-15. Pinning discord.js alone does not pin the rest layer if a transitive dependency floats. ## Installing discord.js and getting a first client online The README points to npm for distribution, and the package name in the repository is discord.js. The install command is the one the npm package page gives for that name. ```bash npm install discord.js ``` The README does not print a code sample, so anything beyond the install step belongs to the guide the README links at discordjs.guide rather than to this repository. What the repository does give you is the package list: the assembled wrapper at packages/discord.js, the gateway wrapper at @discordjs/ws, the REST client at @discordjs/rest, the payload builders at @discordjs/builders, and the voice module at @discordjs/voice. A first real use means picking the assembled wrapper, importing a client from it, and following the guide for intent configuration and event registration. If you would rather not assemble the project yourself, the repository ships create-discord-bot, described as a CLI tool to quickly scaffold a Discord bot project. That is the faster path when you want the build tooling and directory layout decided for you. ## Where discord.js is the wrong tool The library assumes a long-lived process. A gateway client holds a WebSocket open, keeps caches of guilds, channels and members, and reconnects on its own schedule. On a serverless platform that freezes between invocations, that model fights the runtime: you pay for a connection you are not using, and you lose the cache every time the function goes cold. The second constraint is version churn. The README links a v13 to v14 update guide that "includes updated and removed items from the library", which is an admission that upgrading a major version is a migration, not a dependency bump. If your bot is large and you upgrade casually, you will find the breakage at runtime. The third is that the abstraction is opinionated about payloads. @discordjs/builders exists because you are not meant to hand-write raw API JSON. If you want to mirror the Discord API documentation one-to-one, with your own types and no builder layer, the wrapper is between you and the spec. That is the case where @discordjs/core, the thinly abstracted wrapper, is the better entry point from the same repository. ## The alternative inside the same repository The honest comparison is not discord.js against some other language's bot framework. It is discord.js against the lower-level packages the project itself publishes. @discordjs/core gives you the core components of the Discord API with a thin abstraction; @discordjs/rest gives you only the HTTP client, and @discordjs/ws gives you only the gateway. Choosing between them is choosing how much lifecycle you want managed. With discord.js you get the assembled client: caches, event routing, structures, and the builders wired together. With @discordjs/rest you get requests and rate-limit handling and nothing else, which is what you want for a stateless job that posts a message on a schedule and exits. The trade is real in both directions. The thin packages mean less to learn and less to break on upgrade; the assembled client means you are not reimplementing reconnect logic. A second alternative, for teams that want a different runtime rather than a different layer, is another language's library from the community resources list the README links. That is a language decision, not an architectural one, and it should be made before you write commands, not after. ## Maintenance, licence and the cost of staying current The repository is not archived and the last push was on 2026-09-20, so the codebase is being touched. The release cadence visible in the recent list is steady rather than dramatic: 14.27.0 on 2026-07-15, with @discordjs/rest@2.6.2 the same day and 2.6.3 on 2026-07-19. Those are patch releases on a minor line, which is what you want to see between majors. The upgrade cost is concentrated at major boundaries. The README's own pointer to the v13 to v14 update guide tells you the project treats a major as a breaking change set. Budget for reading that guide and for re-testing command registration and event handling, because those are the surfaces most likely to move. The licence is Apache-2.0. That is a permissive licence with an explicit patent grant, and it is compatible with closed-source bot code in the ordinary case. This is not legal advice; if you are redistributing a modified copy of the library itself, or your organisation has a policy on patent clauses, have counsel read the LICENSE file rather than taking a summary from an article. ## Conclusion Adopt discord.js if you are writing a Node.js bot and want the gateway, REST calls, builders and voice handling behind one typed client; the repository is not archived and the last push was on 2026-09-20, with 14.27.0 released on 2026-07-15. Do not adopt it if you want a thin HTTP wrapper with no gateway lifecycle, in which case @discordjs/core or @discordjs/rest from the same monorepo is the smaller surface. Before committing, verify which major version your target runtime supports and read the v13 to v14 update guide, because the project documents breaking changes across majors rather than promising compatibility. ## FAQ ### What is discord.js? It is a Node.js module, written in TypeScript, that lets you interact with the Discord API, and it is the assembled wrapper published from a monorepo that also contains packages for the gateway, REST, builders and voice. ### How do I install discord.js? The README links the npm package page, and the package name is discord.js, so the install is npm install discord.js. The repository also ships a create-discord-bot CLI that scaffolds a bot project if you would rather not set one up by hand. ### how to use discord.js You take the assembled wrapper from packages/discord.js and follow the guide at discordjs.guide, which the README links, for client setup, intents and event handling. The README itself does not print code samples. ### how to use discord js with typescript The library is written in TypeScript and the main package ships types, so a TypeScript project imports the same names as a JavaScript one. The repository itself is a pnpm and turbo workspace, which is the build setup for contributors, not a requirement for consumers. ### Is discord.js a library or a framework? The repository describes it as a module and a wrapper around the Discord API, and the packages list calls @discordjs/core a thinly abstracted wrapper, so the project positions itself as a library rather than a framework that dictates your project structure. ### What version is discord.js on? The most recent release listed for the main package is 14.27.0, published on 2026-07-15, while the @discordjs/rest package is versioned separately and reached 2.6.3 on 2026-07-19. Check the releases page before pinning, because the packages do not share a version number. ## Sources - [discordjs/discord.js on GitHub](https://github.com/discordjs/discord.js) - [License: Apache-2.0](https://github.com/discordjs/discord.js/blob/main/LICENSE) - [Project website](https://discord.js.org) - [README](https://github.com/discordjs/discord.js/blob/main/README.md) - [Releases](https://github.com/discordjs/discord.js/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/discordjs-discord-js