Question 1

How to automatically fix ESLint errors with gulp-eslint?

Accepted Answer

Enable the 'fix' option in the eslint() call, then pipe to gulp.dest to save corrected files. The README references an example in example/fix.js for detailed implementation.

Question 2

gulp-eslint vs running ESLint from CLI – which is better?

Accepted Answer

gulp-eslint is ideal for Gulp users wanting integrated, stream-based linting during builds. For occasional checks or non-Gulp projects, the ESLint CLI or npm scripts are simpler and more direct.

Question 3

Can gulp-eslint handle TypeScript or JSX files?

Accepted Answer

It primarily targets JavaScript files and ignores non-.js extensions by default. For TypeScript, you'd need ESLint with plugins and additional setup, as gulp-eslint doesn't natively support it.

Question 4

How to fail a Gulp build if ESLint finds errors?

Accepted Answer

Use .pipe(eslint.failAfterError()) at the end of your stream. This exits with an error code after processing all files, as demonstrated in the basic usage example in the README.

Question 5

What formatters does gulp-eslint support?

Accepted Answer

It works with ESLint's built-in formatters like 'stylish' and 'checkstyle', or custom formatters via the format() method, providing flexible output options as described in the API.

Question 6

How to customize linting rules per file with gulp-eslint?

Accepted Answer

Use ESLint's .eslintrc files resolved per file directory, or pass rules directly in options. For per-file customization, you might need separate Gulp tasks or conditional logic in your stream.

gulp-eslint

What is gulp-eslint?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions