
Your discord.js bot needs a Node.js version, and the right one changed at the end of October 2026. Node.js 26 became an LTS release on 28 October, Node.js 24 moved to maintenance on 20 October, and Node.js 20 has had no security fixes since 30 April 2026. discord.js itself shipped 14.28.0 on 30 October. Below are the dates from the Node.js release schedule, what each discord.js package asks for, and the commands to move a running bot to a newer Node.js.
Quick answer: Start a new discord.js bot on Node.js 26, the Active LTS line since 28 October 2026 (v26.13.0), supported until 30 April 2029. An existing bot can stay on Node.js 24: it is in maintenance and supported until 30 April 2028. Node.js 22 gets security fixes until 30 April 2027, and Node.js 20 is end of life. The latest discord.js version on npm is 14.28.0; it asks for Node.js 18 or newer, but the current voice packages need Node.js 22, and the development builds of discord.js v15 need Node.js 24.17.0 or newer.
Node.js release status on 3 November 2026
From the Node.js Release working group's schedule and the nodejs.org download index:
| Node.js line | Status | End of life | Latest release | For a discord.js bot |
|---|---|---|---|---|
| 20 (Iron) | End of life since 30 April 2026 | Passed | 20.20.2, 24 March 2026 | Move off it now |
| 22 (Jod) | Maintenance LTS since 21 October 2025 | 30 April 2027 | 22.23.4, 20 October 2026 | Works today, plan the move |
| 24 (Krypton) | Maintenance LTS since 20 October 2026 | 30 April 2028 | 24.22.2, 27 October 2026 | Fine for a running bot |
| 26 (Lithium) | Active LTS since 28 October 2026 | 30 April 2029 | 26.13.0, 28 October 2026 | First choice for a new bot |
| 27 | Alpha since 28 October 2026 | 30 April 2030 (planned) | Alpha builds only | Not for production |
The phases mean different things. Active LTS gets bug fixes and new features that the release team has audited. Maintenance gets critical bug fixes and security updates, with new features only in rare cases that help people migrate. End of life means no fixes at all, security fixes included. Node.js 26 stays in Active LTS until 20 October 2027 and spends its last 18 months in maintenance.
The 26.13.0 release changed nothing from 26.12.1 apart from the LTS metadata, so a bot that ran on 26.12 runs the same on 26.13.
What discord.js 14.28 needs from Node.js
discord.js 14.28.0 was published to npm on 30 October 2026. The engines field in its package.json says "node": ">=18", and the README on the v14 branch says "Node.js 18 or newer is required." The discord.js guide sets a higher bar: it tells you to install the latest LTS version of Node.js, which is now 26.
The packages around discord.js have moved past that minimum. This is what each one declared on npm on 3 November 2026:
| Package | Latest version | Node.js it declares |
|---|---|---|
| discord.js | 14.28.0 (30 October 2026) | 18 or newer |
| @discordjs/rest | 2.6.3 | 18 or newer |
| @discordjs/voice | 0.19.2 | 22.12.0 or newer |
| @discordjs/opus | 0.11.0 (1 November 2026) | 22 or newer |
discord.js v15, dev tag | development build of 2 November 2026 | 24.17.0 or newer |
So a text bot (slash commands, moderation, tickets) still installs on old Node.js versions, while a music or voice bot needs Node.js 22 or newer for the current voice stack. @discordjs/opus 0.11.0 ships prebuilt binaries (Linux, macOS and Windows) for Node.js 22, 24 and 26 only. On any other version its install script falls back to compiling from source, which needs build tools on the server.
By default npm treats engines as advice. When a package's range does not match your Node.js version, npm prints an EBADENGINE warning and installs anyway, so a mismatch can go unnoticed until something breaks at runtime. To make npm stop instead, set your own range in package.json:
"engines": {
"node": ">=24"
}
and turn on strict checking in the project folder:
echo "engine-strict=true" >> .npmrc
With engine-strict=true, npm install refuses to continue when a package's engines range, your own project's included, does not match the running Node.js version.
Node.js 26 vs 24 for a Discord bot
For most discord.js bots the code runs the same on both. These are the differences that matter:
- Support window. Node.js 26 gets fixes until 30 April 2029, a year longer than Node.js 24 (30 April 2028). Node.js 24 is already in maintenance, so it only gets critical fixes and security updates.
- JavaScript engine. Node.js 26.13.0 ships V8 14.6 and Node.js 24.22.2 ships V8 13.6. The Temporal date and time API is on by default in 26, which helps bots that schedule reminders or events across time zones.
- Removals in 26. The
--experimental-transform-typesflag is gone,module.register()now prints a deprecation warning, andhttp.Server.prototype.writeHeader()and the legacy_stream_*modules are removed. If your start command or a dependency uses one of these, test before you switch. - libatomic on Linux. Since Node.js 25 the official Linux binaries are linked against libatomic. If
node -vfails on a minimal Debian or Ubuntu install with an error that mentionslibatomic.so.1, install it withsudo apt install libatomic1. - Native modules. Each major line has its own ABI (137 for Node.js 24, 147 for Node.js 26), so packages with compiled code need a reinstall after the switch. Step 3 below covers that.
TypeScript bots: both lines run .ts files directly through type stripping, which became stable in Node.js 24.12.0 and 25.2.0. It only handles syntax that can be erased. enum declarations and namespaces with runtime code used to need --experimental-transform-types; on Node.js 26 that flag is removed, so run those bots with a tool such as tsx or compile them first.
Which version to pick
- New bot: Node.js 26. It is the latest LTS that the discord.js guide points you to, it has the longest support, and it already meets the 24.17.0 minimum of the v15 development builds.
- Running bot on 24: no rush. Stay on the newest 24.x patch (24.22.2 on 3 November 2026) and move to 26 the next time you update dependencies, well before April 2028.
- Running bot on 22: discord.js 14.28 works, but security fixes stop on 30 April 2027 and the v15 development builds already require 24.17.0. Move to 24 or 26 in the coming months.
- Running bot on 20: no security fixes since 30 April 2026, and the newest @discordjs/voice and @discordjs/opus releases do not support it. Move now.
How to upgrade a live discord.js bot
1. Check what you run now
node -v
npm ls discord.js @discordjs/voice
Log both versions when the bot starts, so the console always shows them:
const { version } = require('discord.js');
console.log(`Node ${process.version}, discord.js ${version}`);
In an ES module, use import { version } from 'discord.js'; instead of require.
On a managed bot plan you do not install Node.js yourself. On our Discord bot hosting you choose the runtime when you set up the bot and the dependencies from package.json are installed when it starts, so that startup line shows which Node.js version your bot got; support can tell you which versions are available.
2. Install the new Node.js on a VPS
On a VPS you manage Node.js yourself. With nvm:
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.8/install.sh | bash
source ~/.nvm/nvm.sh
nvm install 26
nvm alias default 26
node -v
Write the version into the project as well, so your PC and the server use the same one:
echo "26" > .nvmrc
Running nvm use in that folder then picks it up. If a systemd unit starts the bot, its ExecStart line holds the full path to node: replace it with the path that nvm which 26 prints. For PM2, our Node.js PM2 production guide covers the process setup.
3. Reinstall dependencies for the new Node.js
npm ci
npm ci needs a package-lock.json in the project. It deletes node_modules and installs exactly what the lockfile lists, which also downloads or builds native addons for the new Node.js version. If you would rather keep node_modules, run npm rebuild; npm's documentation names a new Node.js version as the typical reason for it.
4. Test with a second bot application
A second process with the same token opens a second gateway session, so both copies can react to the same events. Create a test application in the Discord Developer Portal, invite it to a test server, and run the new Node.js version against that token first.
5. Switch and watch the log
Stop the old process, start the bot on the new Node.js, and read the log for the first hour: deprecation warnings, EBADENGINE lines from the install, and memory use. If you installed the old version with nvm too, it stays installed, so going back is nvm use 24, npm ci and a restart.
The Node.js release schedule after 26
Node.js 26 is the last line on the old model. From Node.js 27 on there is one major release a year: an Alpha phase from October to March for testing breaking changes, a Current release in April, and LTS from October for 30 months. Every release becomes LTS, the odd and even split is gone, and these LTS lines no longer have a separate maintenance phase. Version numbers follow the year of the first Current release: 27.0.0 in 2027, 28.0.0 in 2028. Node.js 27 entered Alpha on 28 October 2026, becomes Current on 22 April 2027 and LTS on 20 October 2027.
For a bot this means one Node.js decision a year. Move to the new LTS line after it is promoted in October, and keep Alpha builds out of production: the Node.js release team says they are meant for library authors and CI pipelines.
FAQ
What is the latest discord.js version on npm in 2026?
14.28.0, published on 30 October 2026. It adds permissions and appPermissions to BaseChannel and backports invite target users and roles. Check your own with npm ls discord.js. Our discord.js v14 guide covers what changed in the v14 line.
Node.js 26 vs 24: which should my Discord bot use? Node.js 26 for a new bot: it is in Active LTS until October 2027 and supported until 30 April 2029. Node.js 24 is fine for a bot that already runs on it; it is supported until 30 April 2028 but only gets critical and security fixes.
Does discord.js still work on Node.js 20? discord.js 14.28.0 still declares Node.js 18 or newer, so a text bot installs and runs. But Node.js 20 has had no security fixes since 30 April 2026, @discordjs/voice 0.19 needs 22.12.0 and @discordjs/opus 0.11.0 needs 22. Upgrade Node.js rather than pinning old voice packages.
Which Node.js version will discord.js v15 need?
v15 is not released yet. Its development builds on npm (the dev tag, 2 November 2026) and the README on the main branch require Node.js 24.17.0 or newer. A bot on Node.js 26 or a current 24.x patch is ready for it.
Do I need to change my bot's code to move from Node.js 22 to 26?
Usually not for a discord.js bot. Check your start command for --experimental-transform-types, watch the log for deprecation warnings, and reinstall dependencies so native modules match the new Node.js version.
How do I see which Node.js version my host runs?
Run node -v in a shell, or log process.version when the bot starts. On a panel host without a shell, the startup log is where you see it.
Sources
All opened on 3 November 2026:
- Node.js: release schedule (nodejs/Release), schedule.json, download index, Node.js 26.13.0 (LTS), Node.js 26.0.0, Evolving the Node.js Release Schedule, End-of-Life, TypeScript in Node.js 26
- discord.js: npm package, v14 package.json, v14 README, main branch README, v14 changelog, guide: installing Node.js and discord.js, @discordjs/voice on npm, @discordjs/opus 0.11.0 release
- npm: package.json engines, engine-strict, engine check in Arborist, npm ci, npm rebuild
- nvm README
- libatomic1: Debian 12, Ubuntu 24.04