node package manager

eslint-loader

eslint-loader Build Status

eslint loader for webpack

Install

$ npm install eslint-loader --save-dev

Usage

In your webpack configuration

module.exports = {
  // ... 
  module: {
    rules: [
      {
        test: /\.js$/,
        exclude: /node_modules/,
        loader: "eslint-loader",
        options: {
          // eslint options (if necessary) 
        }
      },
    ],
  },
  // ... 
}

When using with transpiling loaders (like babel-loader), make sure they are in correct order (bottom to top). Otherwise files will be check after being processed by babel-loader

module.exports = {
  // ... 
  module: {
    rules: [
      {
        test: /\.js$/,
        exclude: /node_modules/,
        use: [
          "babel-loader",
          "eslint-loader",
        ],
      },
    ],
  },
  // ... 
}

To be safe, you can use enforce: "pre" section to check source files, not modified by other loaders (like babel-loader)

module.exports = {
  // ... 
  module: {
    rules: [
      {
        enforce: "pre",
        test: /\.js$/,
        exclude: /node_modules/,
        loader: "eslint-loader",
      },
      {
        test: /\.js$/,
        exclude: /node_modules/,
        loader: "babel-loader",
      },
    ],
  },
  // ... 
}

Options

You can pass eslint options using standard webpack loader options.

Note that the config option you provide will be passed to the CLIEngine. This is a different set of options than what you'd specify in package.json or .eslintrc. See the eslint docs for more detail.

fix (default: false)

This option will enable ESLint autofix feature.

Be careful: this option might cause webpack to enter an infinite build loop if some issues cannot be fixed properly.

cache (default: false)

This option will enable caching of the linting results into a file. This is particularly useful in reducing linting time when doing a full build.

The cache file is written to the ./node_modules/.cache directory.

formatter (default: eslint stylish formatter)

Loader accepts a function that will have one argument: an array of eslint messages (object). The function must return the output as a string. You can use official eslint formatters.

module.exports = {
  entry: "...",
  module: {
    rules: [
      {
        test: /\.js$/,
        exclude: /node_modules/,
        loader: "eslint-loader",
        options: {
          // several examples ! 
 
          // default value 
          formatter: require("eslint/lib/formatters/stylish"),
 
          // community formatter 
          formatter: require("eslint-friendly-formatter"),
 
          // custom formatter 
          formatter: function(results) {
            // `results` format is available here 
            // http://eslint.org/docs/developer-guide/nodejs-api.html#executeonfiles() 
 
            // you should return a string 
            // DO NOT USE console.*() directly ! 
            return "OUTPUT"
          }
        }
      },
    ],
  },
}

eslintPath (default: "eslint")

Path to eslint instance that will be used for linting.

module.exports = {
  entry: "...",
  module: {
    rules: [
      {
        test: /\.js$/,
        exclude: /node_modules/,
        loader: "eslint-loader",
        options: {
          eslintPath: path.join(__dirname, "reusable-eslint-rules.js"),
        }
      },
    ],
  },
  }

Errors and Warning

By default the loader will auto adjust error reporting depending on eslint errors/warnings counts. You can still force this behavior by using emitError or emitWarning options:

emitError (default: false)

Loader will always return errors if this option is set to true.

module.exports = {
  entry: "...",
  module: {
    rules: [
      {
        test: /\.js$/,
        exclude: /node_modules/,
        loader: "eslint-loader",
        options: {
          emitError: true,
        }
      },
    ],
  },
}
emitWarning (default: false)

Loader will always return warnings if option is set to true.

quiet (default: false)

Loader will process and report errors only and ignore warnings if this option is set to true

module.exports = {
  entry: "...",
  module: {
    rules: [
      {
        test: /\.js$/,
        exclude: /node_modules/,
        loader: "eslint-loader",
        options: {
          quiet: true,
        }
      },
    ],
  },
}
failOnWarning (default: false)

Loader will cause the module build to fail if there are any eslint warnings.

module.exports = {
  entry: "...",
  module: {
    rules: [
      {
        test: /\.js$/,
        exclude: /node_modules/,
        loader: "eslint-loader",
        options: {
          failOnWarning: true,
        }
      },
    ],
  },
}
failOnError (default: false)

Loader will cause the module build to fail if there are any eslint errors.

module.exports = {
  entry: "...",
  module: {
    rules: [
      {
        test: /\.js$/,
        exclude: /node_modules/,
        loader: "eslint-loader",
        options: {
          failOnError: true,
        }
      },
    ],
  },
}
outputReport (default: false)

Write the output of the errors to a file, for example a checkstyle xml file for use for reporting on Jenkins CI

The filePath is relative to the webpack config: output.path You can pass in a different formatter for the output file, if none is passed in the default/configured formatter will be used

module.exports = {
  entry: "...",
  module: {
    rules: [
      {
        test: /\.js$/,
        exclude: /node_modules/,
        loader: "eslint-loader",
        options: {
          outputReport: {
            filePath: 'checkstyle.xml',
            formatter: require('eslint/lib/formatters/checkstyle')
          }
        }
      },
    ],
  },
}

Gotchas

NoErrorsPlugin

NoErrorsPlugin prevents webpack from outputting anything into a bundle. So even ESLint warnings will fail the build. No matter what error settings are used for eslint-loader.

So if you want to see ESLint warnings in console during development using WebpackDevServer remove NoErrorsPlugin from webpack config.

Defining configFile or using eslint -c path/.eslintrc

Bear in mind that when you define configFile, eslint doesn't automatically look for .eslintrc files in the directory of the file to be linted. More information is available in official eslint documentation in section Using Configuration Files. See #129.

Changelog

License

Manage permissions for the whole team

Manage developer teams with varying permissions and multiple projects. Learn more about Private Packages and Organizations…

how? learn more

Collaborators list

Stats

Try it out

Keywords

lint, linter, eslint, loader, webpack

Dependencies (5)

loader-fs-cache, loader-utils, object-assign, object-hash, rimraf

Dependents (867)

mnao-builder, justins-react-scripts, @neontribe/react-scripts, ksc-react-scripts, kambi-widget-build-tools, craigsssmith-react-scripts, @stephenjwatkins/react-scripts-augmented, falcor-saddle, nfx-react-scripts, boi-kernel, @chrisdhanaraj/react-scripts, doug-app, react-boot-scripts, @thezanke/react-scripts-pixi, create-react-app-scss-hmr, cooking-lint, tcra, react-webextension-scripts, smoll-react-scripts, yohane, n3tr-react-scripts, yarn-test-1, timer-react-scripts, @jayphelps/react-scripts, @prometheusresearch/react-scripts, fender, @karlhorky/react-scripts, react-material-dashboard, @ashelley/react-scripts-typescript, auth0-react-scripts, react-scripts-custom, aik, bookEU, @samginn/react-scripts, eslint-config-lcy-react, neato, webpack-builder-boilerplate, v-react-scripts, typescript-react-scripts, dooz-eslint-config, rewire-react-scripts, neutrino-preset-base, tars-cli, we-pepper, gerald-react-scripts-fork, amccloud-auth0-react-scripts, qgo, config-react-scripts, hackages, @rubyfans/react-scripts, and more