Adding ESLint with gulp.js

By  on  

I've noticed that I am a loose coder on my personal projects but want some level of decorum on Mozilla and other open source projects.  The more developers you have contributing to a project, the tighter the ship you must keep.  The easiest way to do that is requiring contributions to meet a certain code convention criteria via a tool like ESLint.  Since I like to use gulp.js for my build process, I thought I'd share a very basic use of ESLint for your project.

You start by adding ESLint to your package.json file or installing via NPM manually:

npm install gulp-eslint

With ESLint available somewhere within the node path, you can set up a lint task within your gulpfile.js:

gulp.task('lint', function() {
  return gulp.src('lib/**').pipe(eslint({
    'rules':{
        'quotes': [1, 'single'],
        'semi': [1, 'always']
    }
  }))
  .pipe(eslint.format())
  // Brick on failure to be super strict
  .pipe(eslint.failOnError());
});

You can get a full list of rules and possible values here.  How strict you want to be depends on your general philosophy within JavaScript.  Many people make lint a part of their test task as well so that travis-ci can reject code that isn't up to snuff.

Now that I've written this post, I'll probably take the time to add ESLint to my personal projects so that I can get in the habit of always coding to a certain standard.  Practice makes perfect!

Recent Features

  • By
    An Interview with Eric Meyer

    Your early CSS books were instrumental in pushing my love for front end technologies. What was it about CSS that you fell in love with and drove you to write about it? At first blush, it was the simplicity of it as compared to the table-and-spacer...

  • By
    Page Visibility API

    One event that's always been lacking within the document is a signal for when the user is looking at a given tab, or another tab. When does the user switch off our site to look at something else? When do they come back?

Incredible Demos

  • By
    MooTools 1.3 Browser Object

    MooTools 1.3 was just released and one of the big additions is the Browser object.  The Browser object is very helpful in that not only do you get information about browser type and browser versions, you can gain information about the user's OS, browser plugins, and...

  • By
    Create Custom Events in MooTools 1.2

    Javascript has a number of native events like "mouseover," "mouseout", "click", and so on. What if you want to create your own events though? Creating events using MooTools is as easy as it gets. The MooTools JavaScript What's great about creating custom events in MooTools is...

Discussion

  1. Bradley

    One thing you’d likely want to handle differently is putting your linting rules in the root directory of your project in a file named .eslintrc. Then it’s won’t bloat up your gulpfile if you have lots of rules, stays in your git repos, etc.

    There’s also a .eslintignore to specify directories and files to avoid for linting, for node_modules for example.

  2. I can recommend using lints as Editor/Ide plugins.
    It may be annoying (errors and warning pop up while you write) but on the other hand it helps to learn the style.

    Atom has quite collection of various lints: https://atom.io/users/AtomLinter

  3. nathan

    gulp-eslint has not been updated for a while and still uses ESLint 6 instead of ESLint 8, missing a lot of new features. I would recommend using an alternative that is actively maintained like gulp-eslint-new, or simply running ESLint as an npm task.

Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!