I wrote an error handling utility for my application which is helpful. All my functions are uniquely named against a standard naming convention which helps wit

I wrote an error handling utility for my application which is helpful. All my functions are uniquely named against a standard naming convention which helps with stack traces. For actual debugging I just sprinkle around some console.log statements to see the flow control leading up to the problem. I have an ESLint rule to warn on console statements which makes for easy cleanup. The hardest part of debugging for me, in a peer to peer app, is that the stack trace isn’t going to align with a flow control divided across a network.