I'm working on a web app and setting up a neat bug report feature. I'd like users to submit browser console outputs along with their bug reports. I was hoping to find a straightforward tutorial that explains how to open the developer tools, what they are, and how to copy the information. Instead, I mostly found support pages from different companies, which isn't what I want. I'm thinking of creating a simple website, similar to devtools.how, that introduces dev tools, explains why they're important for bug reporting, and offers links to browser-specific instructions. Does such a resource already exist? If not, I'd love to build it as an open-source project this weekend!
6 Answers
Honestly, it seems unnecessary for users to figure out dev tools. You can just capture console outputs yourself by overriding `console.log`. Tools like Sentry automate this, so your users don’t have to deal with it. It keeps things simpler and error-free without random users needing to copy and paste anything from the console.
I hear you, but I want users to spend just a minute copying the output rather than overwhelming storage with client logs. It's simpler, and I can associate reports with logs.
Honestly, just use Sentry. It does everything you need without any extra hassle on your end.
For most users, wrestling with the dev tools isn't necessary. Instead, use something like Sentry that automatically logs errors and lets you gather breadcrumbs about how they got there. Plus, it allows user feedback that can help trace back to specific sessions.
Great point! That sounds way more efficient than asking users to navigate the dev tools. Just gather the necessary data and logs without putting the onus on them.
If your audience isn’t tech-savvy, asking them to copy messages from the dev tools is a bad move. Instead, implement server-side logging – ask users for basic info like their username and the time of the error so you can easily track it down later.
I don’t think there’s a universal page for this. Most guides are split across various support sites. Creating a simple site with specific steps for each browser and clear visuals would definitely fill a gap!
What? You can use try-catch blocks or error handlers to manage this better instead of needing user intervention!
I think there's been a mix-up here. This is about getting user console errors, not general error handling.
Totally agree with you! I have a client who does the same and only overrides `console.error` and `console.warn`. Regular `console.log` is way too much noise, especially when people forget to clean up debug logs in production!