So you have CI pipeline and want to exit when eslint finds too many warnings?
So eslint has <a target="_blank" href="https://www.eslint.com.cn/docs/2.0.0/user-guide/command-line-interface#:~:text=quiet%20file.js-,%2D%2Dmax%2Dwarnings,with%20a%20success%20exit%20status.">max-warnings</a> arguments in the command line.
<blockquote>
Number of warnings to trigger nonzero exit code
</blockquote>
So if you want to limit warnings of 50, you have to run eslint like
<pre><code class="lang-bash">elsint --max-warnings 10
</code></pre>
But in a real CI pipeline, I think you run eslint with help of npm so
<pre><code class="lang-bash">npx run eslint -- --max-warnings 10
</code></pre>
where npx run eslint command which run your eslint

So you have CI pipeline and want to exit when eslint finds too many warnings?

So eslint has [max-warnings](https://www.eslint.com.cn/docs/2.0.0/user-guide/command-line-interface#:~:text=quiet%20file.js-,%2D%2Dmax%2Dwarnings,with%20a%20success%20exit%20status.) arguments in the command line.

> Number of warnings to trigger nonzero exit code

So if you want to limit warnings of 50, you have to run eslint like

```bash
elsint --max-warnings 10
```

But in a real CI pipeline, I think you run eslint with help of npm so

```bash
npx run eslint -- --max-warnings 10
```

where npx run eslint command which run your eslint

TIL: CI, eslint max count of warning