lint-staged does not detect changed files, skips scripts about lint-staged HOT 4 CLOSED

Is lint-staged not matching against deleted files?

Yep, that's the problem. lint-staged is not matching against files that have been deleted. I verified by making a modification to another file in src/, and then it runs the scripts for src/**/*.

This is not good because it means if I delete files in src/ they lint-staged is silently failing to run needed scripts (f.e. a build script needs to update dist/ based on src/).

This can lead to unexpectedly publishing versions of packages on npm with dist/ folder in incorrect state (and most people are probably not going to test deletion-only commits to realize lint-staged is ignoring them).

from lint-staged.

For now the workaround is I found some other file I could make a change to (without deleting). Now I just need to try and remember this each time I commit; the only reason I discovered it was because I was investigating why the build wasn't outputting certain files, then I decided to test the commit to ensure a version update would include files and discovered the additional lint-staged issue (first my build was discluding some files).

from lint-staged.

You can try overriding the default --diff-filter option to also include deleted files.

EDIT: from the readme:

--diff-filter: By default only files that are added, copied, modified, or renamed are included. Use this flag to override the default ACMR value with something else: added (A), copied (C), deleted (D), modified (M), renamed (R), type changed (T), unmerged (U), unknown (X), or pairing broken (B). See also the git diff docs for --diff-filter.

from lint-staged.

We don't include deleted files by default because the most common linters ESLint and Prettier don't really work when supplied paths that don't exist anymore.

from lint-staged.