Enable "--max-warnings" flag into "next lint" command

[dudusotero]

Describe the feature you'd like to request

I would like to request Max Warnings flag into next lint command.

The main reason for this is to use together with something like lint-staged to validade all my files.

Sometimes I have only warnings but I want stop commit actions like when I have errors.

Describe the solution you'd like

Add a new flag into "Handling warnings" section, like we already have with ---quiet flag.

Describe alternatives you've considered

One idea will be just add a --ignore-warnings flag that will be a boolean value.

But, just use the eslint way will be better due to a entire community already know how to handle this with pure eslint configuration.

[housseindjirdeh]

Added here: #26697 :)

[sstone2423]

This doesn't seem to work unfortunately

[korczas]

next 14 - not working

[vicasas]

@housseindjirdeh This apparently isn't working. I have an application in Next.js that is using lint-staged in conjunction with husky, when committing I would expect it to fail since there are Eslint errors in the code.

I have the following:

const path = require('path')

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

module.exports = {
  '**/*.{js,jsx,ts,tsx}': [buildEslintCommand, 'npm run format:fix'],
  '**/*.{md,mdx,mjs,yml,yaml,css,json}': ['npm run format:fix'],
}

[sstone2423]

Yeah I'm on next 12.3.4 and this isn't working

[parandroid42]

This is still broken in next 14. @housseindjirdeh any chance you could take a look at this again? Thanks!