Question 1

gulp-jshint vs gulp-eslint: which should I use?

Accepted Answer

gulp-jshint is best if you're already using JSHint and Gulp, offering simple integration. gulp-eslint is more modern, with better ES6+ support and a larger plugin ecosystem. For new projects, ESLint is generally recommended due to its active development.

Question 2

How to set up a custom reporter in gulp-jshint?

Accepted Answer

Create a custom reporter using Node.js streams, like with 'map-stream', as shown in the README. Define a function that processes file.jshint results to log errors, then pipe it after jshint() in your Gulp task for customized output.

Question 3

How do I make gulp-jshint fail the build on errors?

Accepted Answer

Use the built-in 'fail' reporter by adding .pipe(jshint.reporter('fail')) after your main reporter in the Gulp pipeline. This causes the task to exit with an error if any JSHint issues are found, enforcing code quality.

Question 4

Can gulp-jshint lint JavaScript inside HTML files?

Accepted Answer

Yes, it can extract JavaScript from HTML files using .pipe(jshint.extract()) before linting. This is useful for web components, and you can control it with flags like 'auto', 'always', or 'never' as per the README.

Question 5

What are the configuration options for gulp-jshint?

Accepted Answer

gulp-jshint passes options directly to JSHint, supporting .jshintrc files and package.json settings. Key plugin options include 'lookup' to control config file searching and 'linter' for alternative linting modules, detailed in the README.

Question 6

Is gulp-jshint compatible with JSX or TypeScript?

Accepted Answer

For JSX, you can use alternative linters like JSXHint via the 'linter' option. For TypeScript, JSHint isn't designed for it, so gulp-jshint isn't suitable; consider gulp-eslint with TypeScript plugins instead.

gulp-jshint

What is gulp-jshint?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions