Advertisement
DoingGoodHelping

Terminal output

Jan 11th, 2021
56
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.73 KB | None | 0 0
  1. GamerBot v1#5972 has logged in.
  2. (node:51416) UnhandledPromiseRejectionWarning: TypeError: Class constructor MessageEmbed cannot be invoked without 'new'
  3. at SayCommand.run (C:\Users\piega\Desktop\Gamerbot V1\GamerBot\src\commands\fun\SayCommand.js:11:30)
  4. at MessageEvent.run (C:\Users\piega\Desktop\Gamerbot V1\GamerBot\src\events\message\MessageEvent.js:17:17)
  5. at Client.emit (events.js:314:20)
  6. at MessageCreateAction.handle (C:\Users\piega\Desktop\Gamerbot V1\GamerBot\node_modules\discord.js\src\client\actions\MessageCreate.js:31:14)
  7. at Object.module.exports [as MESSAGE_CREATE] (C:\Users\piega\Desktop\Gamerbot V1\GamerBot\node_modules\discord.js\src\client\websocket\handlers\MESSAGE_CREATE.js:4:32)
  8. at WebSocketManager.handlePacket (C:\Users\piega\Desktop\Gamerbot V1\GamerBot\node_modules\discord.js\src\client\websocket\WebSocketManager.js:384:31)
  9. at WebSocketShard.onPacket (C:\Users\piega\Desktop\Gamerbot V1\GamerBot\node_modules\discord.js\src\client\websocket\WebSocketShard.js:444:22)
  10. at WebSocketShard.onMessage (C:\Users\piega\Desktop\Gamerbot V1\GamerBot\node_modules\discord.js\src\client\websocket\WebSocketShard.js:301:10)
  11. at WebSocket.onMessage (C:\Users\piega\Desktop\Gamerbot V1\GamerBot\node_modules\ws\lib\event-target.js:132:16)
  12. at WebSocket.emit (events.js:314:20)
  13. (Use `node --trace-warnings ...` to show where the warning was created)
  14. (node:51416) 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: 1)
  15. (node:51416) [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.
  16. (node:51416) UnhandledPromiseRejectionWarning: TypeError: Class constructor MessageEmbed cannot be invoked without 'new'
  17. at SayCommand.run (C:\Users\piega\Desktop\Gamerbot V1\GamerBot\src\commands\fun\SayCommand.js:11:30)
  18. at MessageEvent.run (C:\Users\piega\Desktop\Gamerbot V1\GamerBot\src\events\message\MessageEvent.js:17:17)
  19. at Client.emit (events.js:314:20)
  20. at MessageCreateAction.handle (C:\Users\piega\Desktop\Gamerbot V1\GamerBot\node_modules\discord.js\src\client\actions\MessageCreate.js:31:14)
  21. at Object.module.exports [as MESSAGE_CREATE] (C:\Users\piega\Desktop\Gamerbot V1\GamerBot\node_modules\discord.js\src\client\websocket\handlers\MESSAGE_CREATE.js:4:32)
  22. at WebSocketManager.handlePacket (C:\Users\piega\Desktop\Gamerbot V1\GamerBot\node_modules\discord.js\src\client\websocket\WebSocketManager.js:384:31)
  23. at WebSocketShard.onPacket (C:\Users\piega\Desktop\Gamerbot V1\GamerBot\node_modules\discord.js\src\client\websocket\WebSocketShard.js:444:22)
  24. at WebSocketShard.onMessage (C:\Users\piega\Desktop\Gamerbot V1\GamerBot\node_modules\discord.js\src\client\websocket\WebSocketShard.js:301:10)
  25. at WebSocket.onMessage (C:\Users\piega\Desktop\Gamerbot V1\GamerBot\node_modules\ws\lib\event-target.js:132:16)
  26. at WebSocket.emit (events.js:314:20)
  27. (node:51416) 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)
  28.  
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement