Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/okonet/lint-staged

πŸš«πŸ’© β€” Run linters on git staged files
https://github.com/okonet/lint-staged

developer-experience eslint git linter stage-files stylelint workflow

Last synced: about 1 month ago
JSON representation

πŸš«πŸ’© β€” Run linters on git staged files

Awesome Lists containing this project

README 

        
# πŸš«πŸ’© lint-staged



[![npm version](https://badge.fury.io/js/lint-staged.svg)](https://badge.fury.io/js/lint-staged)



---



Run linters against staged git files and don't let :poop: slip into your code base!



```bash

npm install --save-dev lint-staged # requires further setup

```



```

$ git commit



βœ” Preparing lint-staged...

❯ Running tasks for staged files...

  ❯ packages/frontend/.lintstagedrc.json β€” 1 file

    ↓ *.js β€” no files [SKIPPED]

    ❯ *.{json,md} β€” 1 file

      β Ή prettier --write

  ↓ packages/backend/.lintstagedrc.json β€” 2 files

    ❯ *.js β€” 2 files

      β Ό eslint --fix

    ↓ *.{json,md} β€” no files [SKIPPED]

β—Ό Applying modifications from tasks...

β—Ό Cleaning up temporary files...

```



See asciinema video



[![asciicast](https://asciinema.org/a/199934.svg)](https://asciinema.org/a/199934)



## Why



Linting makes more sense when run before committing your code. By doing so you can ensure no errors go into the repository and enforce code style. But running a lint process on a whole project is slow, and linting results can be irrelevant. Ultimately you only want to lint files that will be committed.



This project contains a script that will run arbitrary shell tasks with a list of staged files as an argument, filtered by a specified glob pattern.



## Related blog posts and talks



- [Introductory Medium post - Andrey Okonetchnikov, 2016](https://medium.com/@okonetchnikov/make-linting-great-again-f3890e1ad6b8#.8qepn2b5l)

- [Running Jest Tests Before Each Git Commit - Ben McCormick, 2017](https://benmccormick.org/2017/02/26/running-jest-tests-before-each-git-commit/)

- [AgentConf presentation - Andrey Okonetchnikov, 2018](https://www.youtube.com/watch?v=-mhY7e-EsC4)

- [SurviveJS interview - Juho VepsΓ€lΓ€inen and Andrey Okonetchnikov, 2018](https://survivejs.com/blog/lint-staged-interview/)

- [Prettier your CSharp with `dotnet-format` and `lint-staged`](https://johnnyreilly.com/2020/12/22/prettier-your-csharp-with-dotnet-format-and-lint-staged)



> If you've written one, please submit a PR with the link to it!



## Installation and setup



To install _lint-staged_ in the recommended way, you need to:



1. Install _lint-staged_ itself:

   - `npm install --save-dev lint-staged`

1. Set up the `pre-commit` git hook to run _lint-staged_

   - [Husky](https://github.com/typicode/husky) is a popular choice for configuring git hooks

   - Read more about git hooks [here](https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks)

1. Install some linters, like [ESLint](https://eslint.org) or [Prettier](https://prettier.io)

1. Configure _lint-staged_ to run linters and other tasks:

   - for example: `{ "*.js": "eslint" }` to run ESLint for all staged JS files

   - See [Configuration](#configuration) for more info



Don't forget to commit changes to `package.json` and `.husky` to share this setup with your team!



Now change a few files, `git add` or `git add --patch` some of them to your commit, and try to `git commit` them.



See [examples](#examples) and [configuration](#configuration) for more information.



## Changelog



See [Releases](https://github.com/okonet/lint-staged/releases).



### Migration



#### v15



- Since `v15.0.0` _lint-staged_ no longer supports Node.js 16. Please upgrade your Node.js version to at least `18.12.0`.



#### v14



- Since `v14.0.0` _lint-staged_ no longer supports Node.js 14. Please upgrade your Node.js version to at least `16.14.0`.



#### v13



- Since `v13.0.0` _lint-staged_ no longer supports Node.js 12. Please upgrade your Node.js version to at least `14.13.1`, or `16.0.0` onward.

- Version `v13.3.0` was incorrectly released including code of version `v14.0.0`. This means the breaking changes of `v14` are also included in `v13.3.0`, the last `v13` version released



#### v12



- Since `v12.0.0` _lint-staged_ is a pure ESM module, so make sure your Node.js version is at least `12.20.0`, `14.13.1`, or `16.0.0`. Read more about ESM modules from the official [Node.js Documentation site here](https://nodejs.org/api/esm.html#introduction).



#### v10



- From `v10.0.0` onwards any new modifications to originally staged files will be automatically added to the commit.

  If your task previously contained a `git add` step, please remove this.

  The automatic behaviour ensures there are less race-conditions,

  since trying to run multiple git operations at the same time usually results in an error.

- From `v10.0.0` onwards, lint-staged uses git stashes to improve speed and provide backups while running.

  Since git stashes require at least an initial commit, you shouldn't run lint-staged in an empty repo.

- From `v10.0.0` onwards, lint-staged requires Node.js version 10.13.0 or later.

- From `v10.0.0` onwards, lint-staged will abort the commit if linter tasks undo all staged changes. To allow creating an empty commit, please use the `--allow-empty` option.



## Command line flags



```

❯ npx lint-staged --help

Usage: lint-staged [options]



Options:

  -V, --version                      output the version number

  --allow-empty                      allow empty commits when tasks revert all staged changes (default: false)

  -p, --concurrent   the number of tasks to run concurrently, or false for serial (default: true)

  -c, --config [path]                path to configuration file, or - to read from stdin

  --cwd [path]                       run all tasks in specific directory, instead of the current

  -d, --debug                        print additional debug information (default: false)

  --diff [string]                    override the default "--staged" flag of "git diff" to get list of files. Implies

                                     "--no-stash".

  --diff-filter [string]             override the default "--diff-filter=ACMR" flag of "git diff" to get list of files

  --max-arg-length [number]          maximum length of the command-line argument string (default: 0)

  --no-stash                         disable the backup stash, and do not revert in case of errors. Implies

                                     "--no-hide-partially-staged".

  --no-hide-partially-staged         disable hiding unstaged changes from partially staged files

  -q, --quiet                        disable lint-staged’s own console output (default: false)

  -r, --relative                     pass relative filepaths to tasks (default: false)

  -x, --shell [path]                 skip parsing of tasks for better shell support (default: false)

  -v, --verbose                      show task output even when tasks succeed; by default only failed output is shown

                                     (default: false)

  -h, --help                         display help for command

```



- **`--allow-empty`**: By default, when linter tasks undo all staged changes, lint-staged will exit with an error and abort the commit. Use this flag to allow creating empty git commits.

- **`--concurrent [number|boolean]`**: Controls the [concurrency of tasks](#task-concurrency) being run by lint-staged. **NOTE**: This does NOT affect the concurrency of subtasks (they will always be run sequentially). Possible values are:

  - `false`: Run all tasks serially

  - `true` (default) : _Infinite_ concurrency. Runs as many tasks in parallel as possible.

  - `{number}`: Run the specified number of tasks in parallel, where `1` is equivalent to `false`.

- **`--config [path]`**: Manually specify a path to a config file or npm package name. Note: when used, lint-staged won't perform the config file search and will print an error if the specified file cannot be found. If '-' is provided as the filename then the config will be read from stdin, allowing piping in the config like `cat my-config.json | npx lint-staged --config -`.

- **`--cwd [path]`**: By default tasks run in the current working directory. Use the `--cwd some/directory` to override this. The path can be absolute or relative to the current working directory.

- **`--debug`**: Run in debug mode. When set, it does the following:

  - uses [debug](https://github.com/visionmedia/debug) internally to log additional information about staged files, commands being executed, location of binaries, etc. Debug logs, which are automatically enabled by passing the flag, can also be enabled by setting the environment variable `$DEBUG` to `lint-staged*`.

  - uses [`verbose` renderer](https://listr2.kilic.dev/renderers/verbose-renderer/) for `listr2`; this causes serial, uncoloured output to the terminal, instead of the default (beautified, dynamic) output.

    (the [`verbose` renderer](https://listr2.kilic.dev/renderers/verbose-renderer/) can also be activated by setting the `TERM=dumb` or `NODE_ENV=test` environment variables)

- **`--diff`**: By default linters are filtered against all files staged in git, generated from `git diff --staged`. This option allows you to override the `--staged` flag with arbitrary revisions. For example to get a list of changed files between two branches, use `--diff="branch1...branch2"`. You can also read more from about [git diff](https://git-scm.com/docs/git-diff) and [gitrevisions](https://git-scm.com/docs/gitrevisions). This option also implies `--no-stash`.

- **`--diff-filter`**: By default only files that are _added_, _copied_, _modified_, or _renamed_ are included. Use this flag to override the default `ACMR` value with something else: _added_ (`A`), _copied_ (`C`), _deleted_ (`D`), _modified_ (`M`), _renamed_ (`R`), _type changed_ (`T`), _unmerged_ (`U`), _unknown_ (`X`), or _pairing broken_ (`B`). See also the `git diff` docs for [--diff-filter](https://git-scm.com/docs/git-diff#Documentation/git-diff.txt---diff-filterACDMRTUXB82308203).

- **`--max-arg-length`**: long commands (a lot of files) are automatically split into multiple chunks when it detects the current shell cannot handle them. Use this flag to override the maximum length of the generated command string.

- **`--no-stash`**: By default a backup stash will be created before running the tasks, and all task modifications will be reverted in case of an error. This option will disable creating the stash, and instead leave all modifications in the index when aborting the commit. Can be re-enabled with `--stash`. This option also implies `--no-hide-partially-staged`.

- **`--no-hide-partially-staged`**: By default, unstaged changes from partially staged files will be hidden. This option will disable this behavior and include all unstaged changes in partially staged files. Can be re-enabled with `--hide-partially-staged`

- **`--quiet`**: Supress all CLI output, except from tasks.

- **`--relative`**: Pass filepaths relative to `process.cwd()` (where `lint-staged` runs) to tasks. Default is `false`.

- **`--shell`**: By default linter commands will be parsed for speed and security. This has the side-effect that regular shell scripts might not work as expected. You can skip parsing of commands with this option. To use a specific shell, use a path like `--shell "/bin/bash"`.

- **`--verbose`**: Show task output even when tasks succeed. By default only failed output is shown.



## Configuration



_Lint-staged_ can be configured in many ways:



- `lint-staged` object in your `package.json`, or [`package.yaml`](https://github.com/pnpm/pnpm/pull/1799)

- `.lintstagedrc` file in JSON or YML format, or you can be explicit with the file extension:

  - `.lintstagedrc.json`

  - `.lintstagedrc.yaml`

  - `.lintstagedrc.yml`

- `.lintstagedrc.mjs` or `lint-staged.config.mjs` file in ESM format

  - the default export value should be a configuration: `export default { ... }`

- `.lintstagedrc.cjs` or `lint-staged.config.cjs` file in CommonJS format

  - the exports value should be a configuration: `module.exports = { ... }`

- `lint-staged.config.js` or `.lintstagedrc.js` in either ESM or CommonJS format, depending on

  whether your project's _package.json_ contains the `"type": "module"` option or not.

- Pass a configuration file using the `--config` or `-c` flag



Configuration should be an object where each value is a command to run and its key is a glob pattern to use for this command. This package uses [micromatch](https://github.com/micromatch/micromatch) for glob patterns. JavaScript files can also export advanced configuration as a function. See [Using JS configuration files](#using-js-configuration-files) for more info.



You can also place multiple configuration files in different directories inside a project. For a given staged file, the closest configuration file will always be used. See ["How to use `lint-staged` in a multi-package monorepo?"](#how-to-use-lint-staged-in-a-multi-package-monorepo) for more info and an example.



#### `package.json` example:



```json

{

  "lint-staged": {

    "*": "your-cmd"

  }

}

```



#### `.lintstagedrc` example



```json

{

  "*": "your-cmd"

}

```



This config will execute `your-cmd` with the list of currently staged files passed as arguments.



So, considering you did `git add file1.ext file2.ext`, lint-staged will run the following command:



`your-cmd file1.ext file2.ext`



### Task concurrency



By default _lint-staged_ will run configured tasks concurrently. This means that for every glob, all the commands will be started at the same time. With the following config, both `eslint` and `prettier` will run at the same time:



```json

{

  "*.ts": "eslint",

  "*.md": "prettier --list-different"

}

```



This is typically not a problem since the globs do not overlap, and the commands do not make changes to the files, but only report possible errors (aborting the git commit). If you want to run multiple commands for the same set of files, you can use the array syntax to make sure commands are run in order. In the following example, `prettier` will run for both globs, and in addition `eslint` will run for `*.ts` files _after_ it. Both sets of commands (for each glob) are still started at the same time (but do not overlap).



```json

{

  "*.ts": ["prettier --list-different", "eslint"],

  "*.md": "prettier --list-different"

}

```



Pay extra attention when the configured globs overlap, and tasks make edits to files. For example, in this configuration `prettier` and `eslint` might try to make changes to the same `*.ts` file at the same time, causing a _race condition_:



```json

{

  "*": "prettier --write",

  "*.ts": "eslint --fix"

}

```



You can solve it using the negation pattern and the array syntax:



```json

{

  "!(*.ts)": "prettier --write",

  "*.ts": ["eslint --fix", "prettier --write"]

}

```



Another example in which tasks make edits to files and globs match multiple files but don't overlap:



```json

{

  "*.css": ["stylelint --fix", "prettier --write"],

  "*.{js,jsx}": ["eslint --fix", "prettier --write"],

  "!(*.css|*.js|*.jsx)": ["prettier --write"]

}

```



Or, if necessary, you can limit the concurrency using `--concurrent ` or disable it entirely with `--concurrent false`.



## Filtering files



Linter commands work on a subset of all staged files, defined by a _glob pattern_. lint-staged uses [micromatch](https://github.com/micromatch/micromatch) for matching files with the following rules:



- If the glob pattern contains no slashes (`/`), micromatch's `matchBase` option will be enabled, so globs match a file's basename regardless of directory:

  - `"*.js"` will match all JS files, like `/test.js` and `/foo/bar/test.js`

  - `"!(*test).js"` will match all JS files, except those ending in `test.js`, so `foo.js` but not `foo.test.js`

  - `"!(*.css|*.js)"` will match all files except CSS and JS files

- If the glob pattern does contain a slash (`/`), it will match for paths as well:

  - `"./*.js"` will match all JS files in the git repo root, so `/test.js` but not `/foo/bar/test.js`

  - `"foo/**/*.js"` will match all JS files inside the `/foo` directory, so `/foo/bar/test.js` but not `/test.js`



When matching, lint-staged will do the following



- Resolve the git root automatically, no configuration needed.

- Pick the staged files which are present inside the project directory.

- Filter them using the specified glob patterns.

- Pass absolute paths to the linters as arguments.



**NOTE:** `lint-staged` will pass _absolute_ paths to the linters to avoid any confusion in case they're executed in a different working directory (i.e. when your `.git` directory isn't the same as your `package.json` directory).



Also see [How to use `lint-staged` in a multi-package monorepo?](#how-to-use-lint-staged-in-a-multi-package-monorepo)



### Ignoring files



The concept of `lint-staged` is to run configured linter tasks (or other tasks) on files that are staged in git. `lint-staged` will always pass a list of all staged files to the task, and ignoring any files should be configured in the task itself.



Consider a project that uses [`prettier`](https://prettier.io/) to keep code format consistent across all files. The project also stores minified 3rd-party vendor libraries in the `vendor/` directory. To keep `prettier` from throwing errors on these files, the vendor directory should be added to prettier's ignore configuration, the `.prettierignore` file. Running `npx prettier .` will ignore the entire vendor directory, throwing no errors. When `lint-staged` is added to the project and configured to run prettier, all modified and staged files in the vendor directory will be ignored by prettier, even though it receives them as input.



In advanced scenarios, where it is impossible to configure the linter task itself to ignore files, but some staged files should still be ignored by `lint-staged`, it is possible to filter filepaths before passing them to tasks by using the function syntax. See [Example: Ignore files from match](#example-ignore-files-from-match).



## What commands are supported?



Supported are any executables installed locally or globally via `npm` as well as any executable from your \$PATH.



> Using globally installed scripts is discouraged, since lint-staged may not work for someone who doesn't have it installed.



`lint-staged` uses [execa](https://github.com/sindresorhus/execa#preferlocal) to locate locally installed scripts. So in your `.lintstagedrc` you can write:



```json

{

  "*.js": "eslint --fix"

}

```



This will result in _lint-staged_ running `eslint --fix file-1.js file-2.js`, when you have staged files `file-1.js`, `file-2.js` and `README.md`.



Pass arguments to your commands separated by space as you would do in the shell. See [examples](#examples) below.



## Running multiple commands in a sequence



You can run multiple commands in a sequence on every glob. To do so, pass an array of commands instead of a single one. This is useful for running autoformatting tools like `eslint --fix` or `stylefmt` but can be used for any arbitrary sequences.



For example:



```json

{

  "*.js": ["eslint", "prettier --write"]

}

```



going to execute `eslint` and if it exits with `0` code, it will execute `prettier --write` on all staged `*.js` files.



This will result in _lint-staged_ running `eslint file-1.js file-2.js`, when you have staged files `file-1.js`, `file-2.js` and `README.md`, and if it passes, `prettier --write file-1.js file-2.js`.



## Using JS configuration files



Writing the configuration file in JavaScript is the most powerful way to configure lint-staged (`lint-staged.config.js`, [similar](https://github.com/okonet/lint-staged#configuration), or passed via `--config`). From the configuration file, you can export either a single function or an object.



If the `exports` value is a function, it will receive an array of all staged filenames. You can then build your own matchers for the files and return a command string or an array of command strings. These strings are considered complete and should include the filename arguments, if wanted.



If the `exports` value is an object, its keys should be glob matches (like in the normal non-js config format). The values can either be like in the normal config or individual functions like described above. Instead of receiving all matched files, the functions in the exported object will only receive the staged files matching the corresponding glob key.



To summarize, by default _lint-staged_ automatically adds the list of matched staged files to your command, but when building the command using JS functions it is expected to do this manually. For example:



```js

export default {

  '*.js': (stagedFiles) => [`eslint .`, `prettier --write ${stagedFiles.join(' ')}`],

}

```



This will result in _lint-staged_ first running `eslint .` (matching _all_ files), and if it passes, `prettier --write file-1.js file-2.js`, when you have staged files `file-1.js`, `file-2.js` and `README.md`.



### Function signature



The function can also be async:



```ts

(filenames: string[]) => string | string[] | Promise

```



### Example: Export a function to build your own matchers



  Click to expand



```js

// lint-staged.config.js

import micromatch from 'micromatch'



export default (allStagedFiles) => {

  const shFiles = micromatch(allStagedFiles, ['**/src/**/*.sh'])

  if (shFiles.length) {

    return `printf '%s\n' "Script files aren't allowed in src directory" >&2`

  }

  const codeFiles = micromatch(allStagedFiles, ['**/*.js', '**/*.ts'])

  const docFiles = micromatch(allStagedFiles, ['**/*.md'])

  return [`eslint ${codeFiles.join(' ')}`, `mdl ${docFiles.join(' ')}`]

}

```



### Example: Wrap filenames in single quotes and run once per file



  Click to expand



```js

// .lintstagedrc.js

export default {

  '**/*.js?(x)': (filenames) => filenames.map((filename) => `prettier --write '${filename}'`),

}

```



### Example: Run `tsc` on changes to TypeScript files, but do not pass any filename arguments



  Click to expand



```js

// lint-staged.config.js

export default {

  '**/*.ts?(x)': () => 'tsc -p tsconfig.json --noEmit',

}

```



### Example: Run ESLint on entire repo if more than 10 staged files



  Click to expand



```js

// .lintstagedrc.js

export default {

  '**/*.js?(x)': (filenames) =>

    filenames.length > 10 ? 'eslint .' : `eslint ${filenames.join(' ')}`,

}

```



### Example: Use your own globs



  Click to expand



It's better to use the [function-based configuration (seen above)](https://github.com/okonet/lint-staged#example-export-a-function-to-build-your-own-matchers), if your use case is this.



```js

// lint-staged.config.js

import micromatch from 'micromatch'



export default {

  '*': (allFiles) => {

    const codeFiles = micromatch(allFiles, ['**/*.js', '**/*.ts'])

    const docFiles = micromatch(allFiles, ['**/*.md'])

    return [`eslint ${codeFiles.join(' ')}`, `mdl ${docFiles.join(' ')}`]

  },

}

```



### Example: Ignore files from match



  Click to expand



If for some reason you want to ignore files from the glob match, you can use `micromatch.not()`:



```js

// lint-staged.config.js

import micromatch from 'micromatch'



export default {

  '*.js': (files) => {

    // from `files` filter those _NOT_ matching `*test.js`

    const match = micromatch.not(files, '*test.js')

    return `eslint ${match.join(' ')}`

  },

}

```



Please note that for most cases, globs can achieve the same effect. For the above example, a matching glob would be `!(*test).js`.



### Example: Use relative paths for commands



  Click to expand



```js

import path from 'path'



export default {

  '*.ts': (absolutePaths) => {

    const cwd = process.cwd()

    const relativePaths = absolutePaths.map((file) => path.relative(cwd, file))

    return `ng lint myProjectName --files ${relativePaths.join(' ')}`

  },

}

```



## Reformatting the code



Tools like [Prettier](https://prettier.io), ESLint/TSLint, or stylelint can reformat your code according to an appropriate config by running `prettier --write`/`eslint --fix`/`tslint --fix`/`stylelint --fix`. Lint-staged will automatically add any modifications to the commit as long as there are no errors.



```json

{

  "*.js": "prettier --write"

}

```



Prior to version 10, tasks had to manually include `git add` as the final step. This behavior has been integrated into lint-staged itself in order to prevent race conditions with multiple tasks editing the same files. If lint-staged detects `git add` in task configurations, it will show a warning in the console. Please remove `git add` from your configuration after upgrading.



## Examples



All examples assume you've already set up lint-staged in the `package.json` file and [husky](https://github.com/typicode/husky) in its own config file.



```json

{

  "name": "My project",

  "version": "0.1.0",

  "scripts": {

    "my-custom-script": "linter --arg1 --arg2"

  },

  "lint-staged": {}

}

```



In `.husky/pre-commit`



```shell

# .husky/pre-commit



npx lint-staged

```



_Note: we don't pass a path as an argument for the runners. This is important since lint-staged will do this for you._



### ESLint with default parameters for `*.js` and `*.jsx` running as a pre-commit hook



  Click to expand



```json

{

  "*.{js,jsx}": "eslint"

}

```



### Automatically fix code style with `--fix` and add to commit



  Click to expand



```json

{

  "*.js": "eslint --fix"

}

```



This will run `eslint --fix` and automatically add changes to the commit.



### Reuse npm script



  Click to expand



If you wish to reuse a npm script defined in your package.json:



```json

{

  "*.js": "npm run my-custom-script --"

}

```



The following is equivalent:



```json

{

  "*.js": "linter --arg1 --arg2"

}

```



### Use environment variables with linting commands



  Click to expand



Linting commands _do not_ support the shell convention of expanding environment variables. To enable the convention yourself, use a tool like [`cross-env`](https://github.com/kentcdodds/cross-env).



For example, here is `jest` running on all `.js` files with the `NODE_ENV` variable being set to `"test"`:



```json

{

  "*.js": ["cross-env NODE_ENV=test jest --bail --findRelatedTests"]

}

```



### Automatically fix code style with `prettier` for any format Prettier supports



  Click to expand



```json

{

  "*": "prettier --ignore-unknown --write"

}

```



### Automatically fix code style with `prettier` for JavaScript, TypeScript, Markdown, HTML, or CSS



  Click to expand



```json

{

  "*.{js,jsx,ts,tsx,md,html,css}": "prettier --write"

}

```



### Stylelint for CSS with defaults and for SCSS with SCSS syntax



  Click to expand



```json

{

  "*.css": "stylelint",

  "*.scss": "stylelint --syntax=scss"

}

```



### Run PostCSS sorting and Stylelint to check



  Click to expand



```json

{

  "*.scss": ["postcss --config path/to/your/config --replace", "stylelint"]

}

```



### Minify the images



  Click to expand



```json

{

  "*.{png,jpeg,jpg,gif,svg}": "imagemin-lint-staged"

}

```



  More about imagemin-lint-staged



[imagemin-lint-staged](https://github.com/tomchentw/imagemin-lint-staged) is a CLI tool designed for lint-staged usage with sensible defaults.



See more on [this blog post](https://medium.com/@tomchentw/imagemin-lint-staged-in-place-minify-the-images-before-adding-to-the-git-repo-5acda0b4c57e) for benefits of this approach.



### Typecheck your staged files with flow



  Click to expand



```json

{

  "*.{js,jsx}": "flow focus-check"

}

```



### Integrate with Next.js



  Click to expand



```js

// .lintstagedrc.js

// See https://nextjs.org/docs/basic-features/eslint#lint-staged for details



const path = require('path')



const buildEslintCommand = (filenames) =>

  `next lint --fix --file ${filenames.map((f) => path.relative(process.cwd(), f)).join(' --file ')}`



module.exports = {

  '*.{js,jsx,ts,tsx}': [buildEslintCommand],

}

```



## Frequently Asked Questions



### The output of commit hook looks weird (no colors, duplicate lines, verbose output on Windows, …)



  Click to expand



Git 2.36.0 introduced a change to hooks where they were no longer run in the original TTY.

This was fixed in 2.37.0:



https://raw.githubusercontent.com/git/git/master/Documentation/RelNotes/2.37.0.txt



> - In Git 2.36 we revamped the way how hooks are invoked. One change

>   that is end-user visible is that the output of a hook is no longer

>   directly connected to the standard output of "git" that spawns the

>   hook, which was noticed post release. This is getting corrected.

>   (merge [a082345372](https://github.com/git/git/commit/a082345372) ab/hooks-regression-fix later to maint).



If updating Git doesn't help, you can try to manually redirect the output in your Git hook; for example:



```shell

# .husky/pre-commit



if sh -c ": >/dev/tty" >/dev/null 2>/dev/null; then exec >/dev/tty 2>&1; fi



npx lint-staged

```



Source: https://github.com/typicode/husky/issues/968#issuecomment-1176848345



### Can I use `lint-staged` via node?



  Click to expand



Yes!



```js

import lintStaged from 'lint-staged'



try {

  const success = await lintStaged()

  console.log(success ? 'Linting was successful!' : 'Linting failed!')

} catch (e) {

  // Failed to load configuration

  console.error(e)

}

```



Parameters to `lintStaged` are equivalent to their CLI counterparts:



```js

const success = await lintStaged({

  allowEmpty: false,

  concurrent: true,

  configPath: './path/to/configuration/file',

  cwd: process.cwd(),

  debug: false,

  maxArgLength: null,

  quiet: false,

  relative: false,

  shell: false,

  stash: true,

  verbose: false,

})

```



You can also pass config directly with `config` option:



```js

const success = await lintStaged({

  allowEmpty: false,

  concurrent: true,

  config: { '*.js': 'eslint --fix' },

  cwd: process.cwd(),

  debug: false,

  maxArgLength: null,

  quiet: false,

  relative: false,

  shell: false,

  stash: true,

  verbose: false,

})

```



The `maxArgLength` option configures chunking of tasks into multiple parts that are run one after the other. This is to avoid issues on Windows platforms where the maximum length of the command line argument string is limited to 8192 characters. Lint-staged might generate a very long argument string when there are many staged files. This option is set automatically from the cli, but not via the Node.js API by default.



### Using with JetBrains IDEs _(WebStorm, PyCharm, IntelliJ IDEA, RubyMine, etc.)_



  Click to expand



_**Update**_: The latest version of JetBrains IDEs now support running hooks as you would expect.



When using the IDE's GUI to commit changes with the `precommit` hook, you might see inconsistencies in the IDE and command line. This is [known issue](https://youtrack.jetbrains.com/issue/IDEA-135454) at JetBrains so if you want this fixed, please vote for it on YouTrack.



Until the issue is resolved in the IDE, you can use the following config to work around it:



husky v1.x



```json

{

  "husky": {

    "hooks": {

      "pre-commit": "lint-staged",

      "post-commit": "git update-index --again"

    }

  }

}

```



husky v0.x



```json

{

  "scripts": {

    "precommit": "lint-staged",

    "postcommit": "git update-index --again"

  }

}

```



_Thanks to [this comment](https://youtrack.jetbrains.com/issue/IDEA-135454#comment=27-2710654) for the fix!_



### How to use `lint-staged` in a multi-package monorepo?



  Click to expand



Install _lint-staged_ on the monorepo root level, and add separate configuration files in each package. When running, _lint-staged_ will always use the configuration closest to a staged file, so having separate configuration files makes sure linters do not "leak" into other packages.



For example, in a monorepo with `packages/frontend/.lintstagedrc.json` and `packages/backend/.lintstagedrc.json`, a staged file inside `packages/frontend/` will only match that configuration, and not the one in `packages/backend/`.



**Note**: _lint-staged_ discovers the closest configuration to each staged file, even if that configuration doesn't include any matching globs. Given these example configurations:



```js

// ./.lintstagedrc.json

{ "*.md": "prettier --write" }

```



```js

// ./packages/frontend/.lintstagedrc.json

{ "*.js": "eslint --fix" }

```



When committing `./packages/frontend/README.md`, it **will not run** _prettier_, because the configuration in the `frontend/` directory is closer to the file and doesn't include it. You should treat all _lint-staged_ configuration files as isolated and separated from each other. You can always use JS files to "extend" configurations, for example:



```js

import baseConfig from '../.lintstagedrc.js'



export default {

  ...baseConfig,

  '*.js': 'eslint --fix',

}

```



To support backwards-compatibility, monorepo features require multiple _lint-staged_ configuration files present in the git repo. If you still want to run _lint-staged_ in only one of the packages in a monorepo, you can either add an "empty" _lint-staged_ configuration to the root of the repo (so that there's two configs in total), or alternatively run _lint-staged_ with the `--cwd` option pointing to your package directory (for example, `lint-staged --cwd packages/frontend`).



### Can I lint files outside of the current project folder?



  Click to expand



tl;dr: Yes, but the pattern should start with `../`.



By default, `lint-staged` executes linters only on the files present inside the project folder(where `lint-staged` is installed and run from).

So this question is relevant _only_ when the project folder is a child folder inside the git repo.

In certain project setups, it might be desirable to bypass this restriction. See [#425](https://github.com/okonet/lint-staged/issues/425), [#487](https://github.com/okonet/lint-staged/issues/487) for more context.



`lint-staged` provides an escape hatch for the same(`>= v7.3.0`). For patterns that start with `../`, all the staged files are allowed to match against the pattern.

Note that patterns like `*.js`, `**/*.js` will still only match the project files and not any of the files in parent or sibling directories.



Example repo: [sudo-suhas/lint-staged-django-react-demo](https://github.com/sudo-suhas/lint-staged-django-react-demo).



### Can I run `lint-staged` in CI, or when there are no staged files?



  Click to expand



Lint-staged will by default run against files staged in git, and should be run during the git pre-commit hook, for example. It's also possible to override this default behaviour and run against files in a specific diff, for example

all changed files between two different branches. If you want to run _lint-staged_ in the CI, maybe you can set it up to compare the branch in a _Pull Request_/_Merge Request_ to the target branch.



Try out the `git diff` command until you are satisfied with the result, for example:



```

git diff --diff-filter=ACMR --name-only master...my-branch

```



This will print a list of _added_, _changed_, _modified_, and _renamed_ files between `master` and `my-branch`.



You can then run lint-staged against the same files with:



```

npx lint-staged --diff="master...my-branch"

```



### Can I use `lint-staged` with `ng lint`



  Click to expand



You should not use `ng lint` through _lint-staged_, because it's designed to lint an entire project. Instead, you can add `ng lint` to your git pre-commit hook the same way as you would run lint-staged.



See issue [!951](https://github.com/okonet/lint-staged/issues/951) for more details and possible workarounds.



### How can I ignore files from `.eslintignore`?



  Click to expand



ESLint throws out `warning File ignored because of a matching ignore pattern. Use "--no-ignore" to override` warnings that breaks the linting process ( if you used `--max-warnings=0` which is recommended ).



#### ESLint < 7



  Click to expand



Based on the discussion from [this issue](https://github.com/eslint/eslint/issues/9977), it was decided that using [the outlined script](https://github.com/eslint/eslint/issues/9977#issuecomment-406420893)is the best route to fix this.



So you can setup a `.lintstagedrc.js` config file to do this:



```js

import { CLIEngine } from 'eslint'



export default {

  '*.js': (files) => {

    const cli = new CLIEngine({})

    return 'eslint --max-warnings=0 ' + files.filter((file) => !cli.isPathIgnored(file)).join(' ')

  },

}

```



#### ESLint >= 7



  Click to expand



In versions of ESLint > 7, [isPathIgnored](https://eslint.org/docs/developer-guide/nodejs-api#-eslintispathignoredfilepath) is an async function and now returns a promise. The code below can be used to reinstate the above functionality.



Since [10.5.3](https://github.com/okonet/lint-staged/releases), any errors due to a bad ESLint config will come through to the console.



```js

import { ESLint } from 'eslint'



const removeIgnoredFiles = async (files) => {

  const eslint = new ESLint()

  const isIgnored = await Promise.all(

    files.map((file) => {

      return eslint.isPathIgnored(file)

    })

  )

  const filteredFiles = files.filter((_, i) => !isIgnored[i])

  return filteredFiles.join(' ')

}



export default {

  '**/*.{ts,tsx,js,jsx}': async (files) => {

    const filesToLint = await removeIgnoredFiles(files)

    return [`eslint --max-warnings=0 ${filesToLint}`]

  },

}

```



#### ESLint >= 8.51.0 && [Flat ESLint config](https://eslint.org/docs/latest/use/configure/configuration-files-new)



  Click to expand



ESLint v8.51.0 introduced [`--no-warn-ignored` CLI flag](https://eslint.org/docs/latest/use/command-line-interface#--no-warn-ignored). It suppresses the `warning File ignored because of a matching ignore pattern. Use "--no-ignore" to override` warning, so manually ignoring files via `eslint.isPathIgnored` is no longer necessary.



```json

{

  "*.js": "eslint --max-warnings=0 --no-warn-ignored"

}

```



**NOTE:** `--no-warn-ignored` flag is only available when [Flat ESLint config](https://eslint.org/docs/latest/use/configure/configuration-files-new) is used.