Support cwd in the top-level CLI

[RainNapper]

The version of ESLint you are using.
7.29.0

The problem you want to solve.
I am working on using eslint as part of an arcanist lint flow. Arcanist runs linters via CLI and translates the output to its own format.

Running eslint via npm requires a specific task to be defined, so we opt to run eslint directly via $repo/node_modules/.bin/eslint, found from utilities like yarn bin

The eslint binary does not accept a --cwd flag, even though the CLIEngine does..

Specifically I am running into an issue with resolving a custom formatter when running outside of the node project directory.

Your take on the correct solution to problem.
Add a CLI flag --cwd which simply forwards that option into CLIEngine.

An example command:

$repo/some-subdir/node_modules/bin/eslint --cwd $repo/some-subdir/ --config '.eslintrc' /$repo/some-subdir/src/index.js

Are you willing to submit a pull request to implement this change?
Yes

[aladdin-add]

just a reminder: CLIEngine has been deprecated, and can no longer be used in the new coming eslint v8.0. see: #13654

[btmills]

The ESLint constructor also supports a cwd option, so I’m not opposed to passing it through the CLI.

In the meantime, you may be able to get this working by passing a path as the --format argument instead of the module name. Here’s the method that loads the formatter, for reference:

eslint/lib/cli-engine/cli-engine.js

Line 983 in 278813a

getFormatter(format) {

[lishichao1002]

I use cwd option in mono repo project

[github-actions]

Oops! It looks like we lost track of this issue. @eslint/eslint-tsc what do we want to do here? This issue will auto-close in 7 days without an update.

[dietergeerts]

@lishichao1002 , how can a cwd option be used? I'm adding a linting package to a mono-repo to check all package, and I can't seem to get it to work.