:nail_care: Run eslint only in the changed parts of the code

Downloads in past


114131.2.16 years ago7 years agoMinified + gzip package size for lint-diff in KB


Build Status
:nailcare: Run eslint only in the changed parts of the code


is a great tool to enforce code style in your code, but it has some limitations: it can only lint entire files. When working with legacy code, we often have to make changes to very large files (which would be too troublesome to fix all lint errors)and thus it would be good to lint only the lines changed and not the entire file.
lint-diff receives a commit range and uses ESLint to lint the changed files and filter only the errors introduced in the commit range (and nothing more).

State of the art

  • lint-staged is a similar tool that lints only the staged changes. It's very helpful for adding a precommit hook, but it cannot be used to enforce the styleguide on a Continuous Integration service like Travis, because the changes are already commited.


  1. Install it:

```sh $ npm install lint-diff ```
  1. Install eslint and add your eslint configuration file.

  1. Use it:

```sh # This will lint the last commit $ lint-diff HEAD^..HEAD ```


  1. Lint the last 3 commits:

```sh $ lint-diff HEAD~3..HEAD ```
  1. Lint local changes that are not yet commited (similar to what lint-staged do):

```sh $ lint-diff HEAD # or $ lint-diff ```
  1. Lint all commits from a build in Travis:

```sh # This environment variable will be available in any Travis build $ lint-diff $TRAVISCOMMITRANGE ```