Advertisement
Luk4O123

Untitled

Nov 29th, 2020
14
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.33 KB | None | 0 0
  1. ReferenceError: fetched is not defined
  2. at NukeCommand.run (C:\Users\Radeon RX580\Desktop\Spirosa\Enigma\src\commands\moderation\NukeCommand.js:26:40)
  3. at processTicksAndRejections (internal/process/task_queues.js:93:5)
  4. (node:11328) UnhandledPromiseRejectionWarning: DiscordAPIError: Unknown Channel
  5. at RequestHandler.execute (C:\Users\Radeon RX580\Desktop\Spirosa\Enigma\node_modules\discord.js\src\rest\RequestHandler.js:154:13)
  6. at processTicksAndRejections (internal/process/task_queues.js:93:5)
  7. at async RequestHandler.push (C:\Users\Radeon RX580\Desktop\Spirosa\Enigma\node_modules\discord.js\src\rest\RequestHandler.js:39:14)
  8. (Use `node --trace-warnings ...` to show where the warning was created)
  9. (node:11328) 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)
  10. (node:11328) [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.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement