he/him 
Is there an existing JS linter that detects dead files and exports?
Show this thread
-
Is there actually a way to statically detect truly “dead” or unused files in a codebase?
Yeah. You can get a list of all the JS files in a project. Then take a list of entry points, get all their transitive dependencies and mark them as "used". Then combine the dependency graph of all entry points, and compare the imports/exports.
-
-
I guess my mind is at those edge cases where a gulpfile or something might reference a file in a unique/untraditional way
-
Yeah dynamic requires are hard. It would need to be customizable with a set of entry points. You could also have a blacklist of files/folders if you're doing anything too tricky. Most large codebases end up with unsued files so it's potentially worth the effort.
- 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.