So I built a small browser‑based tool that takes a JS error and explains it in simpler language. It also suggests possible causes and things to check. Everything runs locally in the browser — no backend, no data stored.
What it does:
Parses the error message
Explains it in plain English
Suggests likely causes
Offers possible next steps
Simple, minimal UI
Works entirely client‑side
I'd appreciate feedback on literally anything on the tool.
Link: https://jsdebugger.netlify.app
There’s a feedback section on the site as well. I’m actively improving it and would love to hear what the HN community thinks.
genezeta•1mo ago
I just tried something like...
...and it warns that it's missing semicolons on all those lines -except for the last one, obviously-. And the fix is... But then I tried something with an actual syntax error.It says...
...which doesn't seem very helpful, not even pointing where in the line the error lies (which acorn does tell you). So I open the dropdown to see the explanation and fixes. The explanation is... ...and the suggested fixes are... So I wonder, what does this actually say beyond the original "syntax error"? How is it helpful at all?Also, looking at the code I find all sort of failing rules which just don't work.
"Assignment in condition":
This will show a warning, while being perfectly fine:
This will not show a warning at all: Then there's the rules for unused variables and for undeclared variables. Those simply do not work at all. They never find anything. It looks like you're expecting acorn to modify your code so that you can later go through it line by line but it just doesn't work that way.