JavaScript Debugger – A tool that explains JavaScript errors in plain English | Hacker News Reader

JavaScript Debugger – A tool that explains JavaScript errors in plain English

1 pointadham_monged1 comment

I’ve been learning frontend development, and one thing that consistently slowed me down was trying to understand JavaScript error messages. Some are clear, but many feel cryptic when you’re still early in your journey. I wanted something that didn’t just tell me what the error was, but why it happened and what I should look at next.

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.

I'm sorry to be so blunt but this seems almost useless.

I just tried something like...

  let someArray = [
    "one",
    "two",
    "three"
  ];

...and it warns that it's missing semicolons on all those lines -except for the last one, obviously-. And the fix is...

  Your code:
  let someArray = [
  Fix:
  let someArray = [;

But then I tried something with an actual syntax error.

It says...

  Syntax Error
  Line 1
  ERROR
  JavaScript cannot read this line because something is typed wrong.

...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...

  The code breaks basic JavaScript rules.

...and the suggested fixes are...

  Fix the typo. Look for missing or extra symbols like ), }, ], or ;.

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:

  if (flag) a = null;

This will not show a warning at all:

  if (a = 2) b = 3;

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.

Reply on news.ycombinator.com