
I Built Myself a Debugging Toolkit — Made With My Claude Friend, Sharing With You
I spend a lot of time debugging things in production. Weird JSON responses, tokens that don't look right, timestamps that make no sense, hashes that need verifying. Every time, it's the same thing — google "base64 decode online", paste sensitive production data into some random website, get the answer, move on. It always felt wrong. So I built Stingr — a toolkit for the stuff I actually need during debugging. Everything runs in your browser, nothing gets sent anywhere. I made it together with Claude (yes, the AI — we're friends now 🤖❤️) and figured I'd share it in case it helps you too. 👉 stingr.dev The tools I actually use at 2am JSON Tree Viewer — this is the one I built first and use most. When a production API returns a massive nested response and I need to find what's wrong, I need to expand/collapse by depth, search for a specific field, pin the paths I keep checking. Recently added JSONPath queries too, so I can do $.data.users[*].errors and get just what I need. JSON Compare —
Continue reading on Dev.to Webdev
Opens in a new tab

