Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- ReferenceError: fetched is not defined
- at NukeCommand.run (C:\Users\Radeon RX580\Desktop\Spirosa\Enigma\src\commands\moderation\NukeCommand.js:26:40)
- at processTicksAndRejections (internal/process/task_queues.js:93:5)
- (node:11328) UnhandledPromiseRejectionWarning: DiscordAPIError: Unknown Channel
- at RequestHandler.execute (C:\Users\Radeon RX580\Desktop\Spirosa\Enigma\node_modules\discord.js\src\rest\RequestHandler.js:154:13)
- at processTicksAndRejections (internal/process/task_queues.js:93:5)
- at async RequestHandler.push (C:\Users\Radeon RX580\Desktop\Spirosa\Enigma\node_modules\discord.js\src\rest\RequestHandler.js:39:14)
- (Use `node --trace-warnings ...` to show where the warning was created)
- (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)
- (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