Javascript Linting with ESLint.

ESLint is a powerful and customizable Javascript linter.

What is a linter ?

Linters are programs that check your source code for syntactic errors and helps you adhere to certain style guidelines. It helps keep your code readable and maintain code quality. Linters are static analysis tools (they inspect the code without executing them) hence, they are available as online programs, as extension/plugins for your favourite code editor, or as a CLI tool.

ESLint is an open source Javascript linter that lets you define your own linting rules. ESLint does not promote any particular coding style although it ships with some built-in rules to get you started.


You need to know Javascript. ESlint is Javascript tool that works on Javascript files.

Installing ESLint

ESLint is written using Node.js and can be installed using npm.

  1. Install ESLint locally
$ npm install eslint --save-dev
  1. Setup a configuration file
$ ./node_modules/.bin/eslint --init

This will create .eslintrc configuration file by guiding you through a brief setup process.

  1. You can run ESLint in your project’s root directory like so
# yourfile.js is the javascript file to be linted.

$ ./node_modules/.bin/eslint yourfile.js

If you want to install ESLint globally than follow these steps:

  1. Install ESLint globally
$ npm install -g eslint
  1. Setup configuration file
$ eslint --init
  1. Run eslint on any file
$ eslint yourfile.js

Cool, but how does it work?

Let's create a demo project to install and use ESLint.

  1. Let's create a directory eslint-demo and initialize npm within project folder.
  1. Install ESLint locally and initialize it.

Open the .eslintrc file and you'll see the following JSON object. ( if you choose to save it as .json file as I did.)

  "env": {
    "browser": true,
    "es6": true
  "extends": "eslint:recommended",
  "parserOptions": {
    "sourceType": "module"
  "rules": {
    "indent": ["error", 4],
    "linebreak-style": ["error", "unix"],
    "quotes": ["error", "double"],
    "semi": ["error", "always"]

ESLint will set up .eslintrc file with some initial settings depending on the options you choose. We can see few properties and their values here. We can change, remove, or override these values.

The first property we see is env, which defines the javascript runtime environment. Here it is set to browser. For Node env will instead have "browser": true, set. By default, ESLint will parse ES5. "es6": true will enable ESLint for ES6.

"env": {
    "browser": true,
    "es6": true

Next extends property extends the recommended rules provided by ESLint.

"extends": "eslint:recommended"

With parserOptions you can define features that are not in ECMAScript 5 by default, such as ES6 syntax, modules, jsx etc.

"rules": {
    "indent": [
    "linebreak-style": [
    "quotes": [
    "semi": [

Finally, we have the rules object. Each rule can be set to one of the three values; error, warn and off. Each rule will check the javascript file for syntactic or logical consistency. To know about what a particular rule does you should refer to this page. Depending on the value set for each rule, ESLint will throw an error if the value of the rule is set as error or warn you for the value set to warn or you can decide not to check for the rule by setting its value off. ESLint is powerful as it allows you to create your own rules.

"env": {
    "browser": true,
    "es6": true

In our .eslintrc file, we have four rules defined in rules object. There are of course more than four rules defined in our config file, as we have extended eslint:recommended property. The rules defined in rules object override the corresponding rules set by eslint:recommended.

Lets lint our code

It's time to test our config. Create a javascript file, yourfile.js with console.log("Hello World") statement and use ESLint on it to check for any errors.

As you can see ESLint throws two errors no-console error & semi error. The no-console error is thrown as ESLint doesn't allow console statements on browser environment. This rule is defined in eslint:recommended property. The semi error is defined in the rules object. It checks for semicolon at the end of the statement and throws an error if it's missing. See how easy it is to get started with ESLint.

If you head over to rules page on ESlint website you can see checkmarks before some rules. If any of these rules throws an error or warning ESlint can fix these rules using ./node_modules/.bin/eslint --fix yourfile.js command.

We see that ESLint fixes the no semicolon error with --fix flag. ESLint won't remove the console.log statement so no-console error is left for the developer to take care of.

We are using ESLint as command line tool, but ESLint can be integrated with your favourite text editor or your favourite build tool as well. This page provides you with the list supported text-editors and recommended extension/plugins for them and information on how you can integrate it with build tools.

Related Resources