lwhiteley / eslint-output Goto Github PK

If I run "eslint-output --max-warnings 0 myfile.js" and there are warnings but no errors, the return code is 0 indicating success.

cosmiconfig version is very old.

• update the package without breaking external interface
• if cannot be avoided then release new major version

I noticed that if we run with maxWarnings set, the command fails but there is no visible message to the user.

For example, I define a script in package.json:

"scripts":{
  "lint": "eslint-output --maxWarnings 150"
}

The output looks like this:

As you see, it is not clear for the user why the lint script failed. Is it possible to print an error message?

If you try directing checkstyle, compact, stylish, or unix output to either the console or a file, both the on-screen and file contents are blank. json, tap, and visualstudio work as expected.

We received a security issue from Dependabot related to y18n:

The npm package y18n before versions 3.2.2, 4.0.1, and 5.0.5 is vulnerable to Prototype Pollution.

I just saw that Dependabot automatically updated y18n in the repo to 4.0.1. Could you please also release a new version to npmjs?

My standard eslint ("lint": "eslint src/**/*.ts src/**/*.tsx",) and my eslint-output "lint:ci": "eslint-output" are finding very different errors. I have a .eslintrc.js file in the same directory as my .eslintoutputrc. I've also tried specifying .eslintrc.js in cliEngineConfig.configFile.

Hi, thanks for this library, I like what it does a lot.

I would love to have command line option to pass in custom path to the .eslintoutputrc file. Is this something you're planning to do? Would you accept PR with this feature?