A Gulp plugin for identifying and reporting on patterns found in ECMAScript/JavaScript code.
First, install gulp-eslint
as a development dependency:
npm install --save-dev gulp-eslint
Then, add it to your gulpfile.js
:
var eslint = require('gulp-eslint');
gulp.task('lint', function () {
gulp.src(['js/**/*.js'])
.pipe(eslint())
.pipe(eslint.format());
});
Or use the plugin API to do things like:
gulp.src('js/**/*.js')
.pipe(eslint({
rulesdir:'custom-rules/',
rules:{
'my-custom-rule': 1,
'strict': 2
},
globals: {
'jQuery':false,
'$':true
},
env:{
browser:true
}
}))
.pipe(eslint.formatEach('compact', process.stderr));
No explicit configuration. A .eslintrc
file my be resolved relative to each linted file.
Type: String
Load additional rules from this directory. For more information, see the eslint CLI readdir option.
Type: String
Path to the eslint rules configuration file. For more information, see the eslint CLI config option and config file info. Note: This file must have a “.json” file extension.
Type: Object
Inline rules configuration. The rule configuration keys must match available validation rules. The associated values should be:
- 0 - turn the rule off
- 1 - turn the rule on as a warning
- 2 - turn the rule on as an error
{
"rules":{
"camelcase": 1,
"no-comma-dangle": 2,
"quotes": 0
}
}
For a list of available rule IDs, see the eslint rules wiki.
Type: Object
Inline globals
configuration. The keys will be considered global variables, and the value determines whether the variable may be reassigned (true) or not (false). For example:
{
"globals":{
"jQuery": false,
"$": true
}
}
Type: Object
Inline env configuration. An env is a preset of rule configurations associated with an JavaScript environment (e.g., node
, browser
). Each key must match an existing env definition, and the key determines whether the env’s rules are applied (true) or not (false).
Type: String
Shorthand for defining options.config
.
Format all linted files once. This should be used in the stream after piping through eslint
; otherwise, this will find no eslint results to format.
The formatter
argument may be a String
, Function
, or undefined
. As a String
, a formatter module by that name or path will be resolved as a module, relative to process.cwd()
, or as one of the eslint-provided formatters. If undefined
, the eslint “compact” formatter will be resolved. A Function
will be called with an Array
of file linting results to format.
// use the default "compact" eslint formatter
eslint.format()
// use the "checkstyle" eslint formatter
eslint.format('checkstyle')
// use the "eslint-path-formatter" module formatter
// (@see https://github.com/Bartvds/eslint-path-formatter)
eslint.format('eslint-path-formatter')
The output
argument may be a WritableStream
, Function
, or undefined
. As a WritableStream
, the formatter results will be written to the stream. If undefined
, the formatter results will be written to gulp’s log. A Function
will be called with the formatter results as the only parameter.
// write to gulp's log (default)
eslint.format();
// write messages to stdout
eslint.format('junit', process.stdout)
Format each linted file individually. This should be used in the stream after piping through eslint
; otherwise, this will find no eslint results to format.
The arguments for formatEach
are the same as the arguments for format
.
##Configuration
Eslint may be configured explicity by using any of the following plugin options: config
, rules
, globals
, or env
. When not configured in this way, eslint will attempt to resolve a file by the name of .eslintrc
within the same directory as the file to be linted. If not found there, parent directories will be searched until .eslintrc
is found or the directory root is reached. Any configuration will expand upon the default eslint configuration.