Better way to trace errors in Meteor methods?

I’m finding errors thrown by Meteor methods to not be very useful:

I’m guessing that since it’s a DDP call, it can’t really tell from what point on the client this particular method call originated. Line 76 in SignupPage.js is just my console.error(e) statement. Is there a reliable way to tell which specific method call caused this validation error?