Error Discord.js-commando

c-sharp

#1

(node:218) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'finalize' of null
at SQLiteProvider.destroy (/rbd/pnpm-volume/58e5ca18-71e6-4777-91bb-9bcc72c12ef7/node_modules/.registry.npmjs.org/discord.js-commando/0.10.0/node_modules/discord.js-commando/src/providers/sqlite.js:124:29)
at CommandoClient.destroy (/rbd/pnpm-volume/58e5ca18-71e6-4777-91bb-9bcc72c12ef7/node_modules/.registry.npmjs.org/discord.js-commando/0.10.0/node_modules/discord.js-commando/src/client.js:175:41)
at <anonymous>
(node:218) 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(). (rejection id: 4)
(node:218) UnhandledPromiseRejectionWarning: Error [WS_CONNECTION_TIMEOUT]: The connection to the gateway timed out.
at Timeout.setTimeout (/rbd/pnpm-volume/58e5ca18-71e6-4777-91bb-9bcc72c12ef7/node_modules/.github.com/discordjs/discord.js/b5d5c699e65bf14a77065a75aabd24e4972988a9/node_modules/discord.js/src/client/Client.js:261:16)
at ontimeout (timers.js:498:11)
at Timer.unrefdHandle (timers.js:611:5)
(node:218) 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(). (rejection id: 5)
a few seconds ago

(node:316) UnhandledPromiseRejectionWarning: TypeError: this.fetchUser is not a function
at CommandoClient.once (/rbd/pnpm-volume/58e5ca18-71e6-4777-91bb-9bcc72c12ef7/node_modules/.registry.npmjs.org/discord.js-commando/0.10.0/node_modules/discord.js-commando/src/client.js:84:11)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:111:20)
at CommandoClient.emit (events.js:208:7)
at WebSocketManager.triggerReady (/rbd/pnpm-volume/58e5ca18-71e6-4777-91bb-9bcc72c12ef7/node_modules/.github.com/discordjs/discord.js/b5d5c699e65bf14a77065a75aabd24e4972988a9/node_modules/discord.js/src/client/websocket/WebSocketManager.js:253:17)
at WebSocketManager.checkReady (/rbd/pnpm-volume/58e5ca18-71e6-4777-91bb-9bcc72c12ef7/node_modules/.github.com/discordjs/discord.js/b5d5c699e65bf14a77065a75aabd24e4972988a9/node_modules/discord.js/src/client/websocket/WebSocketManager.js:224:61)
at Object.module.exports [as GUILD_CREATE] (/rbd/pnpm-volume/58e5ca18-71e6-4777-91bb-9bcc72c12ef7/node_modules/.github.com/discordjs/discord.js/b5d5c699e65bf14a77065a75aabd24e4972988a9/node_modules/discord.js/src/client/websocket/handlers/GUILD_CREATE.js:11:17)
at WebSocketManager.handlePacket (/rbd/pnpm-volume/58e5ca18-71e6-4777-91bb-9bcc72c12ef7/node_modules/.github.com/discordjs/discord.js/b5d5c699e65bf14a77065a75aabd24e4972988a9/node_modules/discord.js/src/client/websocket/WebSocketManager.js:201:31)
at WebSocketShard.onPacket (/rbd/pnpm-volume/58e5ca18-71e6-4777-91bb-9bcc72c12ef7/node_modules/.github.com/discordjs/discord.js/b5d5c699e65bf14a77065a75aabd24e4972988a9/node_modules/discord.js/src/client/websocket/WebSocketShard.js:259:29)
at WebSocketShard.onMessage (/rbd/pnpm-volume/58e5ca18-71e6-4777-91bb-9bcc72c12ef7/node_modules/.github.com/discordjs/discord.js/b5d5c699e65bf14a77065a75aabd24e4972988a9/node_modules/discord.js/src/client/websocket/WebSocketShard.js:310:10)
(node:316) 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(). (rejection id: 1)
(node:316) [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.

I Need Help.


MOD EDIT: formatting


#2

Hi @BlankSans, welcome to the Glitch Forums!

When I take a look at your project I see a different set of errors than the ones that you’ve listed here, including ones that reference an invalid token. I don’t know much about discord-js.commando (and maybe someone else here does) but it seems logical that if your token is incorrect the CommandoClient might not be properly initialized and you’d see an error like this.