I was tired of debugging production issues blindly in my frontend projects.
So I built a small SDK for myself that:
It’s still early, but it’s already helping me debug much faster.
Thinking of improving it further.
🌐 Dashboard (Try it here): https://bugtrace.jainprashuk.in/
📦 NPM Package (SDK): https://www.npmjs.com/package/bug-tracker-sdk
📚 Documentation: https://bugtrace.jainprashuk.in/
If anyone here is interested in trying something like this or sharing feedback, let me know 👀
Adarsh Kant
Building AnveVoice - Voice OS for websites. Solo founder. Building in public.
The "works on my machine" problem hits different when you're dealing with frontend issues across browsers, devices, and screen readers. Error tracking + screenshot capture at the moment of failure is exactly what most debugging workflows are missing.
We ran into this constantly while building AnveVoice — our AI voice assistant takes real DOM actions on websites (clicks, fills forms, navigates), and the behavior differences across Chrome, Safari, and Firefox were brutal. A user would report "it doesn't click the right button" and we'd see zero issues locally. Adding session replay and DOM state snapshots at the point of failure completely changed our debugging speed.
One suggestion: if you're capturing screenshots, consider also logging the DOM tree state at that moment. For accessibility-heavy apps especially, the visual screenshot alone doesn't tell you about missing ARIA labels or broken focus states that cause failures for assistive tech users. That's a gap most error tracking tools still ignore.