唯然

have you tried [--no-error-on-unmatched-pattern](https://eslint.org/docs/user-guide/command-line-interface#--no-error-on-unmatched-pattern) (it was introduced in eslint v6.8.0)?

As of now, eslint mix linting rules and config related problems to the output. But you just want to disallow the former (please correct if I'm misunderstanding). If you want...

IMHO, it does not make sense to be just logged, as in most cases it was an error to pass ignored files to eslint.

the more cases are users misconfigured the eslintignore. Imagine this: the file `foo.js` was ignored, users ran `eslint foo.js` output 0 warning/error. they might think it was linted successfully, but...

I'm willing to take this one. ;) There are mainly 2 ways to publish esm: 1. esm only 2. dual mode (esm and cjs) From a maintainer's perspective, I slightly...

Given eslint v8 has dropped Node.js < v12(and will likely drop

Is there anything blocking converting eslint configs/plugins to esm? Or it will just take a bit longer? As more packages are going to be esm-only(i.e. babel https://github.com/babel/babel/issues/11701#issuecomment-777118858), I was concerned...

To clarify, eslint has supported esm for a long while(`parserOptions.sourceType: "module"`). The point here: esm-only eslint is moving the eslint community (plugins/configs/parsers/...) to esm.

friendly ping @mysticatea : are you still working on this? it seems very useful! 👍

you don't have to create 2 instances. `lintText/lintFiles` won't modify your files, see how eslint cli works: https://github.com/eslint/eslint/blob/52226593974fc7fcb60f1be73b165863b3d1a7fb/lib/cli.js#L292-L307