discord.js is a powerful Node.js module that allows you to easily interact with the Discord API.

#jeez like what the

~ $ node storage/shared/stuff/hazy/hazy.js
(node:5452) UnhandledPromiseRejectionWarning: ReferenceError: AbortController is not defined
    at RequestHandler.execute (/storage/emulated/0/stuff/hazy/node_modules/discord.js/src/rest/RequestHandler.js:172:15)
    at RequestHandler.execute (/storage/emulated/0/stuff/hazy/node_modules/discord.js/src/rest/RequestHandler.js:176:19)
    at RequestHandler.push (/storage/emulated/0/stuff/hazy/node_modules/discord.js/src/rest/RequestHandler.js:50:25)
    at async WebSocketManager.connect (/storage/emulated/0/stuff/hazy/node_modules/discord.js/src/client/websocket/WebSocketManager.js:128:9)
    at async Client.login (/storage/emulated/0/stuff/hazy/node_modules/discord.js/src/client/Client.js:245:7)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:5452) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:5452) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

discord.js version

dont know, maybe the newest

Node.js version

dont know, maybe thhhe newest

Operating system

android (termux application)

Priority this issue should have

High (immediate attention needed)

Which partials do you have configured?

USER, CHANNEL, GUILD_MEMBER, MESSAGE, REACTION

Which gateway intents are you subscribing to?

GUILDS, GUILD_MEMBERS, GUILD_EMOJIS_AND_STICKERS, GUILD_INTEGRATIONS, GUILD_WEBHOOKS, GUILD_INVITES, GUILD_VOICE_STATES, GUILD_PRESENCES, GUILD_MESSAGES, GUILD_MESSAGE_REACTIONS, GUILD_MESSAGE_TYPING, DIRECT_MESSAGES, DIRECT_MESSAGE_REACTIONS, DIRECT_MESSAGE_TYPING

I have tested this issue on a development release

i dont know what is this

Please describe the problem you are having in as much detail as possible: When I start my bot sharded bot (in 4240 servers), one of the shards times out and stops starting. This issue is persistent across all versions of djs, including 12. The timeout happens around 90% of the time I start the shards. Here are the errors and messages I receive in the console for that shard.

Error: Shard 1's Client took too long to become ready. Error: Something took too long to do. Left a guild called undefined.

The last message is me logging the guild leave event, which also seems to be firing from that specific shard.

Include a reproducible code sample here, if possible:

My Sharding File (Code for version 11):

const { ShardingManager } = require('discord.js');
const manager = new ShardingManager('./bot.js', { token: process.env.TOKEN });

manager.spawn(20); // Start 4 Shards
manager.on('launch', shard => console.log("Sharding Manager ➜".bold.brightYellow, `Launched shard ${shard.id}`.bold.brightCyan));

Code for Ready event:

client.login(process.env.TOKEN).catch(console.error)

client.on('ready', (i, callback) => {
    functions.log(`Online in ${client.guilds.size} servers!`)

    blapi.handle(client, apiKeys, 10);

    setTimeout(() => {
        /* Bot Presence (Game and Status) */
        client.shard.fetchClientValues('guilds.size').then(results => {

            let servercount = results.reduce((prev, guildCount) => prev + guildCount, 0)

            client.user.setPresence({
                game: {
                type: 0,
                name: game + " | " + servercount
                //name: 'Discord API Error ➜ https://status.discordapp.com'
                },
                status: status
            });

            if (client.shard.id === 3) {
                Glenn.updateStats(servercount, client.shard.count);
                functions.postStats(client)
                functions.log(`Posted ${servercount} servers!`)
            }
        })
    },60000);
});

The error is persistent across different IP addresses and computers, and I get no email from discord.

Further details:

• discord.js version: 11.4.2, 11.5.1, 11.6.1, 12, 12.0.2
• Node.js version: v12.15.0
• Operating system: Ubuntu & Mac
• Priority this issue should have – please be realistic and elaborate if possible: Not sure...

• [x] I have also tested the issue on latest master, commit hash:

Please describe the problem you are having in as much detail as possible:

All of a sudden the "guildMemberSpeaking" stopped working. The bot was running did not crash, no errors, all of a sudden the event stop working. It will however emit once when a user starts talking but never will again for that user.

The following is an example of my entire test bot to show the issue:

const path = require('path');
SERVER_DIST = (path.basename(__filename) == "bot.js" ? "prod" : "beta");
CONFIG = require('./config.js').loadVar(SERVER_DIST);

const Discord = require('discord.js');
const client = new Discord.Client();

client.on('error', console.error);

client.on('ready', () => {
	console.log(`Logged in as ${client.user.tag}!`);
	let voiceChan = client.channels.get(CONFIG.ids.mainVoiceChanID);
	voiceChan.join().then(connection => {
		console.log('Connected to voice channel.');
	}).catch(err => console.log(err)); 
});

client.on('guildMemberSpeaking', (member, speaking) => {
	if(speaking) {
		console.log(member.displayName + ' started talking.');    
	}
	else {
		console.log(member.displayName + ' stopped talking');
	}
});

client.login(CONFIG.discordApi.token);

Further details:

• discord.js version: 11.5.1
• Node.js version: v10.15.3
• Operating system: CentOS release 6.10 (Final)
• Priority this issue should have – please be realistic and elaborate if possible: We use this event to track voice activity in a voice channel, this is very important to this bots usage.

• [ ] I have also tested the issue on latest master, commit hash:

Which package is this bug report for?

discord.js

Issue description

After around 5-6 hours of running, my discord bot decides to randomly exit with an exit code of 0. There is nothing in my code that should cause that, and adding a debug event listener shows the bot failing around a websocket reacquisition near the 6 hour mark.

I have tried running my bot with typescript, I've tried compiling the code to javascript and running that, I've tried packaging it as a docker container and running that locally, I've tried packing it as a docker container and running that on my production server. Every environment and method results in the same issue.

Bot code

https://github.com/NeonWizard/sockbot-discord

Logs

[WS => Shard 0] Heartbeat acknowledged, latency of 86ms.
[WS => Shard 0] [HeartbeatTimer] Sending a heartbeat.
[WS => Shard 0] Heartbeat acknowledged, latency of 89ms.
[WS => Shard 0] [HeartbeatTimer] Sending a heartbeat.
[WS => Shard 0] Heartbeat acknowledged, latency of 85ms.
[WS => Shard 0] [HeartbeatTimer] Sending a heartbeat.
[WS => Shard 0] Heartbeat acknowledged, latency of 83ms.
[WS => Shard 0] [HeartbeatTimer] Sending a heartbeat.
[WS => Shard 0] Heartbeat acknowledged, latency of 84ms.
[WS => Shard 0] [RECONNECT] Discord asked us to reconnect
[WS => Shard 0] [DESTROY]
    Close Code    : 4000
    Reset         : false
    Emit DESTROYED: true
[WS => Shard 0] Clearing the heartbeat interval.
[WS => Shard 0] [WebSocket] Destroy: Attempting to close the WebSocket. | WS State: OPEN      
[WS => Shard 0] [WebSocket] Close: Tried closing. | WS State: CLOSING
[WS => Shard 0] [WebSocket] Adding a WebSocket close timeout to ensure a correct WS reconnect.
        Timeout: 5000ms
[WS => Shard 0] [WebSocket] Clearing the close timeout.
[WS => Shard 0] [WebSocket] Close Emitted: false
[WS => Shard 0] [WebSocket] did not close properly, assuming a zombie connection.
Emitting close and reconnecting again.
[WS => Shard 0] [CLOSE]
    Event Code: 1011
    Clean     : false
    Reason    : INTERNAL_ERROR
[WS => Shard 0] Session id is present, attempting an immediate reconnect...
[WS => Shard 0] [CONNECT]
    Gateway    : wss://gateway.discord.gg/
    Version    : 10
    Encoding   : json
    Compression: none
[WS => Shard 0] Setting a HELLO timeout for 20s.
[WS => Shard 0] [CONNECTED] Took 146ms
[WS => Shard 0] Clearing the HELLO timeout.
[WS => Shard 0] Setting a heartbeat interval for 41250ms.
[WS => Shard 0] [RESUME] Session REDACTED, sequence 51
[WS => Shard 0] [RESUMED] Session REDACTED | Replayed 1 events.       
[WS => Shard 0] [ResumeHeartbeat] Sending a heartbeat.
[WS => Shard 0] Heartbeat acknowledged, latency of 88ms.
[WS => Shard 0] Clearing the heartbeat interval.
[WS => Shard 0] [CLOSE]
    Event Code: 4000
    Clean     : true
    Reason    :
[WS => Shard 0] Session id is present, attempting an immediate reconnect...
[WS => Shard 0] An open connection was found, attempting an immediate identify.
[WS => Shard 0] [RESUME] Session REDACTED, sequence 52
root@ruby:/home/spooky#

Code sample

https://github.com/NeonWizard/sockbot-discord

Package version

[email protected]

Node.js version

v16.16.0, [email protected]

Operating system

Windows (WSL), Linux (Ubuntu), Docker (node:lts-alpine)

Priority this issue should have

High (immediate attention needed)

Which partials do you have configured?

No Partials

Which gateway intents are you subscribing to?

Guilds, GuildMessages, GuildMessageReactions, MessageContent

I have tested this issue on a development release

No response

Issue description

I have a bot with clicks on buttons every second and people executing commands. This generally goes very well, but sometimes I get an "Unknown Interaction" when I defer to it.

I've been debugging for the past three days and can't seem to understand why it's happening. My last possible explanation is an error in Discord.js or on the side of Discord.

I have attached a few screenshots describing the error

I would prefer to know if this is due to my code, or Discord.js or Discord itself.

Code sample

// Button Handler
        if(interaction.isButton()) {
            console.log(customId);
            const button = client.buttons.get(customId);
            if(!button) return;

            let {
                cooldown = -1,
                deferUpdate = false
            } = button;

            if(deferUpdate) {
                console.error('defer button');
                const testHook = interaction;
                console.error(interaction.member.user.username, interaction.member.id)
                await interaction.deferUpdate();
                console.error("doei", interaction.member.user.username, interaction.member.id)
                
            }
            
            let buttonName = (customId.startsWith('games-all-')) ? "btn-games-all" : "btn-" + customId;
            console.log(buttonName);
            if(!cooldownButtons.has(buttonName)) {
                console.log(buttonName, 'add cooldown')
                cooldownButtons.set(buttonName, new Collection());
            }

            const currentBtnTime = Date.now();
            const timestamps = await cooldownButtons.get(buttonName);
            const cooldownAmount = (cooldown) * 1000;

            if(timestamps.has(member.id)) {
                console.log(member.id, 'heeft cooldown')
                const expirationTime = timestamps.get(member.id) + cooldownAmount;

                if(currentBtnTime < expirationTime) {
                    console.log(member.id, 'heeft cooldown')
                    const time_left = (expirationTime - currentBtnTime) / 1000;

                    if(deferUpdate) {
                        return interaction.followUp({content: `**Cooldown:** You have to wait ${time_left.toFixed(1)} seconds.`, ephemeral: true});
                    }else{
                        return interaction.followUp({content: `**Cooldown:** You have to wait ${time_left.toFixed(1)} seconds.`, ephemeral: true});
                    }
                }
            }else{
                timestamps.set(member.id, currentBtnTime);
                setTimeout(() => timestamps.delete(member.id), cooldownAmount);

                try{
                    await button.execute(interaction);
                }catch(error) {
                    console.error(error);
                }
            }
        }

discord.js version

13.3.1

Node.js version

16.13.0

Operating system

Debian 10

Priority this issue should have

Medium (should be fixed soon)

Which partials do you have configured?

CHANNEL, GUILD_MEMBER, MESSAGE, REACTION

Which gateway intents are you subscribing to?

GUILDS, GUILD_MEMBERS, GUILD_INVITES, GUILD_VOICE_STATES, GUILD_MESSAGES, GUILD_MESSAGE_REACTIONS, DIRECT_MESSAGES

I have tested this issue on a development release

No response

My issue seems related to issue #225.

The bot will run and show as logged in for a channel for some time and then it will suddenly drop offline. However, it will still post messages that are scheduled to a text channel.

autoReconnect is set to true as well.

For a look at my bot see: https://github.com/ericnelson0/GoHBot/blob/master/index.js

Please describe the problem you are having in as much detail as possible:

Since several weeks (about 3 weeks) my spam bot reconnection to Discord, it happens a few hours or a few minutes after the launch of the shards (Less shards the more it will take time to spam reconnection) I have not made any modification for 4 weeks on my bot so I wonder if it comes from discord directly or from my code.

I have already run it locally and same problem and several of my friends have the same problem on a different library of discord (eris) but also on discord.js

Namely I use Discord.js 11.6.4

I currently have 25 servers so I launched my bot plus 25 shards I had no problem for 2-3 minutes then the shards were restarted one after the other.

Namely that I'm not testing another bot on the same VPS or PC

https://imgur.com/c2Xbf0l.png

Further details:

• discord.js version: 11.6.5
• Node.js version: 12.16.1
• Operating system: Linux Debian (VPS) Windows 10 (Local)
• Priority this issue should have - please be realistic and elaborate if possible: On a scale of 1 to 10 I would say 6/10

Translated with www.DeepL.com/Translator (free version)

• Added Permission#toArray.
• Allow singular PermissionResolvables as parameter to Permissions#missing.
• Fix JSDoc.
• Allow Permissions to be iterated over.
• Removed unnecessary (and bugged) conditional statement in constructor. (could accept negative bitfields before)
• Updated typings will be submitted as a PR when/if this one gets merged.

Semantic versioning classification:

• [x] This PR changes the library's interface (methods or parameters added)
  • [ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
• [ ] This PR only includes non-code changes, like changes to documentation, README, etc.

Starting with v13.0.0 the minimum node version requirement for discord.js will be >=16.6.0 to make use of features like optional chaining, (ES2021) etc.

Benefits:

• Full access to ES2021 features

Drawbacks:

• Dropping node 12 support
• Dropping node 14 support

Please describe the changes this PR makes and why it should be merged:

Status

This will need #4879 before it lands.

• [x] Code changes have been tested against the Discord API, or there are no code changes
• [ ] I know how to update typings and have done so, or typings don't need updating

Semantic versioning classification:

• [x] This PR changes the library's interface (methods or parameters added)
  • [ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
• [ ] This PR only includes non-code changes, like changes to documentation, README, etc.

Please describe the problem you are having in as much detail as possible: I am getting ratelimited by discord for an unknown reason As said here it should never happen but I do not know why this is happening for me https://github.com/discordjs/discord.js/blob/6be5051f9296fe9a10549f2f9a11c18776b1b617/src/rest/RequestHandler.js#L149

For more information, it's happening frequently at 00:00 GMT

I am also having a lot of 500 errors when this is happening.

Include a reproducible code sample here, if possible:

429 hit on route /gateway/bot

Code : 500
AbortError: The user aborted a request.
at RequestHandler.execute (/home/koyamie/Koya/node_modules/discord.js/src/rest/RequestHandler.js:106:9)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:93:5)

Further details:

• discord.js version: lastest master
• Node.js version: 12.13.0
• Operating system: debian 9
• Priority this issue should have – please be realistic and elaborate if possible:

• [x] I have also tested the issue on latest master, commit hash:

Please describe the changes this PR makes and why it should be merged:

• https://github.com/discord/discord-api-docs/pull/5821

Status and versioning classification:

• Code changes have been tested against the Discord API, or there are no code changes
• I know how to update typings and have done so, or typings don't need updating

Which package is this bug report for?

discord.js

Issue description

1. Install latest version of discord.js
2. Enable Channel partial
3. Run the bot and wait for DM

ERROR Uncaught Exception: TypeError: Cannot read properties of undefined (reading 'id')
    at DMChannel._patch (./node_modules/discord.js/src/structures/DMChannel.js:39:36)
    at new BaseChannel (./node_modules/discord.js/src/structures/BaseChannel.js:25:38)
    at new DMChannel (./node_modules/discord.js/src/structures/DMChannel.js:17:5)
    at createChannel (./node_modules/discord.js/src/util/Channels.js:30:17)
    at ChannelManager._add (./node_modules/discord.js/src/managers/ChannelManager.js:50:21)
    at MessageCreateAction.getPayload (./node_modules/discord.js/src/client/actions/Action.js:29:22)
    at MessageCreateAction.getChannel (./node_modules/discord.js/src/client/actions/Action.js:38:12)
    at MessageCreateAction.handle (./node_modules/discord.js/src/client/actions/MessageCreate.js:9:26)
    at module.exports [as MESSAGE_CREATE] (./node_modules/discord.js/src/client/websocket/handlers/MESSAGE_CREATE.js:4:32)
    at WebSocketManager.handlePacket (./node_modules/discord.js/src/client/websocket/WebSocketManager.js:352:31)

Code sample

No response

Package version

14.7.2-dev.1672747445-7dec892.0

Node.js version

18.12.1

Operating system

No response

Priority this issue should have

Medium (should be fixed soon)

Which partials do you have configured?

Channel

Which gateway intents are you subscribing to?

Guilds, GuildMembers, GuildPresences, GuildMessages, DirectMessages, MessageContent

I have tested this issue on a development release

7dec892

Please describe the changes this PR makes and why it should be merged: This has been possible since 9922151266a8ac618f41b7583c984a8755eccf14

I have tested locally using docker build -t discordjs/proxy:latest -f packages/proxy-container/Dockerfile . and the image still builds.

Status and versioning classification:

• Code changes have been tested against the Discord API, or there are no code changes
• I know how to update typings and have done so, or typings don't need updating
• This PR only includes non-code changes, like changes to documentation, README, etc.

Please describe the changes this PR makes and why it should be merged: Closes #8960.

Ended up taking a different approach than what was originally proposed with https://github.com/discordjs/discord.js/issues/8960#issuecomment-1363232818 and later discussed internally.

The new WebSocketManager#fetchStatus method and the new HeartbeatComplete event should be more than enough for all intents and purposes. I can't really envision what else you might want to track that you can't accomplish with the tools already provided, otherwise.

Status and versioning classification:

• Code changes have been tested against the Discord API, or there are no code changes
• I know how to update typings and have done so, or typings don't need updating
• This PR changes the library's interface (methods or parameters added)

Please describe the changes this PR makes and why it should be merged: Another big stepping stone in prod usability - this time for folks trying to scale.

Status and versioning classification:

• Code changes have been tested against the Discord API, or there are no code changes
• I know how to update typings and have done so, or typings don't need updating
• This PR changes the library's interface (methods or parameters added)