Improve error debugging
As you can see in the screenshot, I have an interaction handler that runs the various handlers of my slash commands, like autocomplete.
There's a bug in the code causing the debugger to stop (break on caught and uncaught exceptions).
The problem is that I can't tell from the call stack where this error was originally thrown.
I don't know if this is because of how I load commands dynamically similar to the docs or because of the underlying EventEmitter.
How can I change my code so I can see in the call stack where the error originates from in my code?
I'm not talking about "error handling" - this is only for debugging and not for output for users.
I'd also prefer not to litter my code with individual
There's a bug in the code causing the debugger to stop (break on caught and uncaught exceptions).
The problem is that I can't tell from the call stack where this error was originally thrown.
I don't know if this is because of how I load commands dynamically similar to the docs or because of the underlying EventEmitter.
How can I change my code so I can see in the call stack where the error originates from in my code?
I'm not talking about "error handling" - this is only for debugging and not for output for users.
I'd also prefer not to litter my code with individual
try-catch
Support server for discord.js, a Node.js module to interact with Discord's apps API.
57,915Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
