Make sure that you are using a version of Node.js supported by your version of ESLint. See prerequisites for ESLint 8 and ESLint 9. For TypeScript support, you need TypeScript 4.8 or later.
To install gulp-eslint-new, use npm:
npm i -D gulp-eslint-new
gulp-eslint-new will also install the latest version of ESLint 9, unless another one is found. To use a particular version of ESLint, install it by yourself. For example, to use ESLint 8.8.0:
npm i -D gulp-eslint-new eslint@8.8.0
If you are migrating from gulp-eslint, you probably won't need to make any substantial changes to your gulp task, as the API is widely compatible.
Note though that many options have changed: the current options are documented in the gulpESLintNew(options)
section.
Also note that gulp-eslint-new is designed to work with ESLint 8 or 9, whereas the latest release of gulp-eslint only supports ESLint 6: you will need to update your project to address breaking changes in ESLint. You can follow the links below for more information.
- Breaking changes for users from ESLint 6 to ESLint 7
- Breaking changes for users from ESLint 7 to ESLint 8
- Breaking changes for users from ESLint 8 to ESLint 9
const { src } = require('gulp');
const gulpESLintNew = require('gulp-eslint-new');
// Define the default gulp task.
exports.default =
() =>
src(['scripts/*.js']) // Read files.
.pipe(gulpESLintNew({ fix: true })) // Lint files, create fixes.
.pipe(gulpESLintNew.fix()) // Fix files if necessary.
.pipe(gulpESLintNew.format()) // Output lint results to the console.
.pipe(gulpESLintNew.failAfterError()); // Exit with an error if problems are found.
Or use the plugin API to do things like:
// gulpfile.mjs
import js from '@eslint/js';
import jquery from 'eslint-plugin-jquery';
import globals from 'globals';
import gulp from 'gulp';
import gulpESLintNew from 'gulp-eslint-new';
export default
() =>
gulp.src(['**/*.{js,mjs}', '!node_modules/**'])
.pipe
(
gulpESLintNew
(
{
configType: 'flat',
overrideConfig:
[
js.configs.recommended,
jquery.configs.slim,
{
languageOptions:
{
globals:
{
...globals.browser,
...globals.jquery,
chrome: 'readonly',
},
},
rules: { 'strict': 'error' },
},
],
plugins: { jquery },
warnIgnored: true,
},
),
)
.pipe(gulpESLintNew.formatEach('compact', process.stderr));
For additional examples, look through the example directory.
Run ESLint with default settings. A configuration file will be resolved depending on the version of ESLint used.
Param type: Record<string, unknown>
Run ESLint with the specified options. All supported options are listed below. See the linked content for details about each option.
General options
File enumeration options
ignore
ignorePath
(not in flat config)ignorePatterns
(flat config only)
Linting options
allowInlineConfig
baseConfig
overrideConfig
overrideConfigFile
plugins
reportUnusedDisableDirectives
(not in flat config)resolvePluginsRelativeTo
(not in flat config)ruleFilter
(flat config only)rulePaths
(not in flat config)stats
(flat config only)useEslintrc
(not in flat config)
Autofix options
Reporting options
Other options
Type: "eslintrc" | "flat" | null
ESLint supports two types of configuration: a new config type, aka flat config, based on file eslint.config.*
, and a legacy config type, or eslintrc config, based on file .eslintrc
.
In ESLint 8, the default config type is the legacy config, and the new config is partly supported depending on the version of ESLint used.
To use the the new config with ESLint 8 in gulp-eslint-new, set the option configType
to "flat"
.
ESLint 9 uses the new config type by default.
To use the legacy config with ESLint 9 in gulp-eslint-new, set the option configType
to "eslintrc"
.
The new and legacy config types differ significantly in the available options and their usage. Refer to the respective documentation in ESLint for the specifics of each options.
Type: string
The working directory. This must be an absolute path. Default is the current working directory.
The working directory is where ESLint will look for a .eslintignore
file by default.
It is also the base directory for any relative paths specified in the options (e.g. overrideConfigFile
, resolvePluginsRelativeTo
, rulePaths
, overrideConfig.extends
, etc.).
The location of the files to be linted is not related to the working directory.
Type: boolean
When false
, ESLint will not respect .eslintignore
files or ignore patterns in your configurations.
Type: string
The path to a file ESLint uses instead of .eslintignore
in the current working directory.
This option in not available when configType
is "flat"
.
Type: string[] | null
Ignore file patterns to use in addition to config ignores.
This option in only available when configType
is "flat"
.
Type: boolean | (message: LintMessage) => boolean
Set to true
or a function to generate fixes when possible, or set to false
to explicitly disable autofixing.
If a predicate function is present, it will be invoked once for each lint message, and only the lint messages for which the function returned true
will be reported.
See the Autofix section for more information and examples.
Type: ("directive" | "problem" | "suggestion" | "layout")[] | null
The types of fixes to apply. Default is all types.
Type: boolean
When true
, this option will filter warning messages from ESLint results. This mimics the ESLint CLI --quiet
option.
Type: (message: LintMessage, index: number, list: LintMessage[]) => unknown
When a function is provided, it will be used to filter ESLint result messages, removing any messages that do not return a true
(or truthy) value.
Type: boolean
When true
, add a result warning when ESLint ignores a file. Default is false
.
This can be used to find files that are needlessly being loaded by gulp.src
.
For example, since ESLint automatically ignores file paths inside a node_modules
directory but gulp.src
does not, a gulp task may take seconds longer just reading files from node_modules
.
Param type: string
Shorthand for defining options.overrideConfigFile
.
Param type: (result: Object) => void
Call a function for each ESLint file result. No returned value is expected. If an error is thrown, it will be wrapped in a gulp PluginError
and emitted from the stream.
gulp.src(['**/*.js', '!node_modules/**'])
.pipe(gulpESLintNew())
.pipe
(
gulpESLintNew.result
(
result =>
{
// Called for each ESLint result.
console.log(`ESLint result: ${result.filePath}`);
console.log(`# Messages: ${result.messages.length}`);
console.log
(
`# Warnings: ${result.warningCount} (${
result.fixableWarningCount} fixable)`,
);
console.log
(
`# Errors: ${result.errorCount} (${
result.fixableErrorCount} fixable, ${
result.fatalErrorCount} fatal)`,
);
},
),
);
Param Type: (result: Object, callback: Function) => void
Call an asynchronous, Node-style callback-based function for each ESLint file result. The callback must be called for the stream to finish. If an error is passed to the callback, it will be wrapped in a gulp PluginError
and emitted from the stream.
Param Type: (result: Object) => Promise<void>
Call an asynchronous, promise-based function for each ESLint file result. If the promise is rejected, the rejection reason will be wrapped in a gulp PluginError
and emitted from the stream.
Param type: (results: Object[]) => void
Call a function once for all ESLint file results before a stream finishes. No returned value is expected. If an error is thrown, it will be wrapped in a gulp PluginError
and emitted from the stream.
The results list has additional properties that indicate the number of messages of a certain kind.
errorCount |
number of errors |
warningCount |
number of warnings |
fixableErrorCount |
number of fixable errors |
fixableWarningCount |
number of fixable warnings |
fatalErrorCount |
number of fatal errors |
gulp.src(['**/*.js', '!node_modules/**'])
.pipe(gulpESLintNew())
.pipe
(
gulpESLintNew.results
(
results =>
{
// Called once for all ESLint results.
console.log(`Total Results: ${results.length}`);
console.log
(
`Total Warnings: ${results.warningCount} (${
results.fixableWarningCount} fixable)`,
);
console.log
(
`Total Errors: ${results.errorCount} (${
results.fixableErrorCount} fixable, ${
results.fatalErrorCount} fatal)`,
);
},
),
);
Param type: (results: Object[], callback: Function) => void
Call an asynchronous, Node-style callback-based function once for all ESLint file results before a stream finishes. The callback must be called for the stream to finish. If an error is passed to the callback, it will be wrapped in a gulp PluginError
and emitted from the stream.
Param type: (results: Object[]) => Promise<void>
Call an asynchronous, promise-based function once for all ESLint file results before a stream finishes. If the promise is rejected, the rejection reason will be wrapped in a gulp PluginError
and emitted from the stream.
Stop a task/stream if an ESLint error has been reported for any file.
// Cause the stream to stop (fail) without processing more files.
gulp.src(['**/*.js', '!node_modules/**'])
.pipe(gulpESLintNew())
.pipe(gulpESLintNew.failOnError());
Stop a task/stream if an ESLint error has been reported for any file, but wait for all of them to be processed first.
// Cause the stream to stop (fail) when the stream ends if any ESLint error(s)
// occurred.
gulp.src(['**/*.js', '!node_modules/**'])
.pipe(gulpESLintNew())
.pipe(gulpESLintNew.failAfterError());
formatter
param type: string | Object | Function | undefined
writer
param type: NodeJS.WritableStream | Function | undefined
Format all linted files once.
This should be used in the stream after piping through gulpESLintNew
; otherwise, this will find no ESLint results to format.
The formatter
argument determines the ESLint formatter used to format linting results.
If a string
is provided, a formatter module by that name or path will be resolved.
The resolved formatter will be either one of the built-in ESLint formatters, or a formatter exported by a module with the specified path (located relative to the ESLint working directory), or a formatter exported by a package installed as a dependency (the prefix "eslint-formatter-" in the package name can be omitted).
Instead of providing a string, it is also possible to specify a formatter object as resolved by the ESLint method loadFormatter
, or a formatter function directly.
If this argument is undefined
, a modified version of the ESLint "stylish" formatter will be used.
// Use the default gulp-eslint-new formatter.
gulpESLintNew.format()
// Use the "html" ESLint formatter.
gulpESLintNew.format('html')
// Use "eslint-formatter-pretty" as a formatter (must be installed with `npm`).
// See https://www.npmjs.com/package/eslint-formatter-pretty.
gulpESLintNew.format('pretty')
The writer
argument may be a writable stream, Function
, or undefined
.
As a writable stream, the formatter output will be written to the stream.
If undefined
, the formatter output will be written to gulp's log.
A Function
will be called with the formatter output as the only parameter.
// write to gulp's log (default)
gulpESLintNew.format()
// write messages to stdout
gulpESLintNew.format('junit', process.stdout)
formatter
param type: string | Object | Function | undefined
writer
param type: NodeJS.WritableStream | Function | undefined
Format each linted file individually.
This should be used in the stream after piping through gulpESLintNew
; otherwise, this will find no ESLint results to format.
The arguments for gulpESLintNew.formatEach
are the same as the arguments for gulpESLintNew.format
.
Overwrite files with the fixed content provided by ESLint.
This should be used in conjunction with the option fix
in gulpESLintNew(options)
.
Files without a fix and files that were not processed by ESLint will be left untouched.
See the Autofix section for more information and examples.
ESLint can fix some lint problems automatically: this function is called autofix.
To enable autofix with gulp-eslint-new, set the option fix
to true
in gulpESLintNew(options)
, then pipe the stream to gulpESLintNew.fix()
, e.g.
gulp.src(['**/*.{js,ts}', '!node_modules/**'])
.pipe(gulpESLintNew({ fix: true }))
.pipe(gulpESLintNew.fix());
See also the autofix examples.
The fix
option applies fixes to the gulp stream.
gulpESLintNew.fix()
saves the fixed content to file.
Rules that are fixable can be found in ESLint's rules list.
When fixes are applied, a fixed
property is set to true
on the fixed file's ESLint result.
ESLint results are attached as an eslint
property to the Vinyl files that pass through a gulp stream pipeline.
This is available to streams that follow the initial gulp-eslint-new stream.
The functions gulpESLintNew.result
and gulpESLintNew.results
are made available to support extensions and custom handling of ESLint results.