Course contentsShow
← JavaScript
Lesson 2564 of 2,72352. Linting and FormattingFree lesson

Interpreting ESLint Error Messages

Read and understand ESLint output, including rule names, line numbers, and how to look up rule documentation.

Interpreting ESLint Error Messages

You'll learn how to read ESLint's output to quickly identify problems and find solutions.

Understanding the Error Format

When ESLint finds issues in your code, it reports them in a structured format. Each error message contains three critical pieces of information: the file path and line number where the problem exists, the rule name that was violated, and a plain-English description of what went wrong.

A typical error looks like this:

/path/to/file.js
  12:5  error  'userName' is assigned a value but never used  no-unused-vars

Breaking Down the Message

The format follows a pattern: line:column severity message rule-name

  • 12:5 tells you the problem is on line 12, column 5
  • error indicates severity (could also be "warning")
  • 'userName' is assigned... explains what's wrong in human terms
  • no-unused-vars is the rule identifier you can look up

Finding Rule Documentation

The rule name (like no-unused-vars) is your key to deeper understanding. You can search for it directly on ESLint's website or use the pattern: https://eslint.org/docs/rules/[rule-name]

The documentation explains why the rule exists, shows examples of correct and incorrect code, and lists any configuration options you can adjust.

Think of It Like a GPS

ESLint errors work like navigation instructions: they pinpoint exactly where you are (line and column), what's wrong (the message), and what rule of the road you broke (the rule name). The rule name is your map to understanding the full context.

Key Takeaway: ESLint errors provide file location, line/column numbers, a description, and most importantly—a rule name you can look up to understand the issue fully and decide whether to fix it or disable the rule.