YoJxsn

Untitled

Nov 4th, 2020
20
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.18 KB | None | 0 0
  1. rowing 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: 1)
  2. (node:222016) [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.
  3. (node:222016) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'first' of undefined
  4. at KickCommand.run (C:\Users\beast\OneDrive\Desktop\BOT\Craig\src\commands\moderation\KickCommand.js:11:53)
  5. at MessageEvent.run (C:\Users\beast\OneDrive\Desktop\BOT\Craig\src\events\message\message.js:17:17)
  6. at Client.emit (events.js:315:20)
  7. at MessageCreateAction.handle (C:\Users\beast\OneDrive\Desktop\BOT\Craig\node_modules\discord.js\src\client\actions\MessageCreate.js:31:14)
  8. at Object.module.exports [as MESSAGE_CREATE] (C:\Users\beast\OneDrive\Desktop\BOT\Craig\node_modules\discord.js\src\client\websocket\handlers\MESSAGE_CREATE.js:4:32)
  9. at WebSocketManager.handlePacket (C:\Users\beast\OneDrive\Desktop\BOT\Craig\node_modules\discord.js\src\client\websocket\WebSocketManager.js:384:31)
  10. at WebSocketShard.onPacket (C:\Users\beast\OneDrive\Desktop\BOT\Craig\node_modules\discord.js\src\client\websocket\WebSocketShard.js:444:22)
  11. at WebSocketShard.onMessage (C:\Users\beast\OneDrive\Desktop\BOT\Craig\node_modules\discord.js\src\client\websocket\WebSocketShard.js:301:10)
  12. at WebSocket.onMessage (C:\Users\beast\OneDrive\Desktop\BOT\Craig\node_modules\ws\lib\event-target.js:125:16)
  13. at WebSocket.emit (events.js:315:20)
  14. (node:222016) 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)
Add Comment
Please, Sign In to add comment