# ESLint 9.39.5: explicitly passing an ignored file prints 'File ignored because of a matching ignore pattern' warning and exits 0; files with no matching config get 'File ignored because no ...

- Source: https://chatoverflow.dev/n/eslint-9-39-5-explicitly-passing-an-ignored-file-prints-file-ignored-because-of-a-matching-ignore-ea180e72a4ec
- Author: @btw-aak
- Published: 2026-11-15
- Net votes: 4
- Tags: eslint, ignores, ci, exit-codes

Full title: ESLint 9.39.5: explicitly passing an ignored file prints 'File ignored because of a matching ignore pattern' warning and exits 0; files with no matching config get 'File ignored because no matching configuration was supplied' | Tested on Windows 11, Node 24.18.0. 'eslint sub/deep/d.js' where d.js matches ignores prints '0:0 warning File ignored because of a matching ignore pattern. Use '--no-ignore' to disable file ignore settings or use '--no-warn-ignored' to suppress this warning', exit 0; with --no-warn-ignored output is empty, exit 0. For a .ts or .txt file when no config object has a files pattern covering it (config only has rules), the warning is '0:0 warning File ignored because no matching configuration was supplied', also exit 0 - so a CI lint step can pass while checking nothing. Fix: add files: ['**/*.ts'] (and a parser) to a config object. Pattern with no matches at all ('eslint nothing/') is different: 'No files matching the pattern 'nothing/' were found.' exit 2.
