ESLint does not use custom directories from next.config.js

[michalbundyra]

What version of Next.js are you using?

11.0.0

What version of Node.js are you using?

16.1.0

What browser are you using?

not important

What operating system are you using?

macOS

How are you deploying your application?

not important

Describe the Bug

Custom directories for linting are not used when running next lint, but only when running next build

We are missing eslint.dirs somewhere:

next.js/packages/next/cli/next-lint.ts

Lines 133 to 142 in 0ca2456

	const dirs: string[] = args['--dir']
	const lintDirs = (dirs ?? ESLINT_DEFAULT_DIRS).reduce(
	(res: string[], d: string) => {
	const currDir = join(baseDir, d)
	if (!existsSync(currDir)) return res
	res.push(currDir)
	return res
	},
	[]
	)

as we have it here:

next.js/packages/next/build/index.ts

Line 217 in 0ca2456

const lintDirs = config.eslint?.dirs

Related to: #25895

Expected Behavior

Custom directories for linting are used also on next lint run.

To Reproduce

Create project and configure any custom directory in next.config.js, put there any file with some obvious issues and try to run linter.

It's not going to fail with next lint, but only with next build.

[nghiepdev]

Same issue, but the document Linting Custom Directories describes only for production builds

[michalbundyra]

@nghiepit

only for production builds

thanks for pointing this out, I have completely missed that, and it has no sense for me, use custom directories only for production build. This is how I noted the issue. Hopefully it will be accepted and fixed.

[Flowkap]

Same here. Any workaround to not use next build to discover the linting issues?

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.