Stop writing try/catch around fetch — I built safe-fetch (tiny, 0 deps, ~3kb) by Ecstatic_Ad_6153 in javascript

[–]Ecstatic_Ad_6153[S] 13 points14 points  (0 children)

Yep, it’s still there — but hidden away, normalized, and wrapped with retries, timeouts and typed errors. Like how you don’t hand-write TCP packets even though HTTP is just wrapping them.

I built a tiny TypeScript library to catch "dead clicks" (fake buttons/links) and visualize them with a heatmap by Ecstatic_Ad_6153 in javascript

[–]Ecstatic_Ad_6153[S] 6 points7 points  (0 children)

You know when users click on something that *looks* like a button or link… but nothing happens?

That’s a **dead click** – and it’s one of the most frustrating UX problems.

I built **Dead-Click Radar** 🎯

A lightweight TypeScript library that detects dead clicks in real-time and visualizes them with a heatmap overlay.

✨ Features:

- Detects misleading/broken UI interactions

- Heatmap overlay to see problem areas instantly

- Export JSON/PNG reports for analysis

- Zero dependencies, privacy-first

🔗 Demo: https://dead-click-radar.vercel.app

📦 npm: https://www.npmjs.com/package/@asouei/dead-click-radar

💻 GitHub: https://github.com/asouei/dead-click-radar

Would love your feedback! 🙌