Results doesn't match when running eslint directly

[manuel-mauky]

When I'm running the normal eslint, I get different results compared to eslint-nibble.
For example, in my code base when I'm running eslint I get 367 warnings, many of which are related to the jsdoc/no-undefined-types rule. But when I run eslint-nibble --no-interactive --rule jsdoc/no-undefined-types ./**/*.ts it shows No lint failures found for rule(s): jsdoc/no-undefined-types .

When I run eslint-nibble ./**/*.ts it prints:

> eslint-nibble ./**/*.ts


16 files checked.  10 passed.  6 failed.  6 warnings.  0 errors.

? Which rule would you like to view? (Use arrow keys)
❯ null: 6|       

Not sure what null means here but when I try to select this and press enter the tool exits without any further info.
Also "16 files checked" seems to indicate that not everything is checked at all. In my code base there are thousands of files.

I wasn't able to reproduce this in a small example project so maybe it's only happening in big projects?

[IanVS]

Hmmmm, yeah that's a bit tough to troubleshoot without a reproduction. What version of eslint are you using, and what type of config file?

[ChristianUlbrich]

@manuel-mauky While I also do not know your codebase, your installed version of eslint (and probably also the version of typescript-eslint and for that matter, the used version of typescript as well), I have a feeling, that it is related to #117.

Briefly looking at #117 and actually using eslint-nibble with a current eslint@9 things might get even more complicated, because I get other error messages as well...

• 'extensions' has been removed

what would probably warrant a new issue altogether...