This is a tool to scan the Dart project and determine if there are unused files, assets, dependencies etc.
It will parse all the Dart files and find all the imported files in parallel. After gathering all the data, it will start with the entry file and follow paths imported files and determine which ones are actually used and which are not.
NOTE: This method is not perfect as there are other ways to import packages. To combat this, the tool also checks if the file contains the name of the package. While not perfect it does find some edge cases.
- Find unused files
- Find unused dependencies
- Find unused assets
- Find GetIt entries registered but never used
- Find unused ARB file entries used for localisation
- Determine if there are unused imports in the files
- by analysing the code
- by using
dart/flutter analyzeand ensure that the unused imports config is enabled
- Improve check for unused assets
- Assets path can be assigned to a variable and hence imported but actually never used anywhere in the code
- Test against Dart/Flutter packages
- Output as warning instead of erroring
- Available as a Github Action
- Specify config
- Handle flavours
- Able to specify entry file
dart-unused [OPTIONS] --path
Options: -p, --path Path to the Dart project
--remove
Remove all unreferenced items discovered
-a, --assets Check for unreferenced assets
-d, --deps Check for unreferenced dependencies
-l, --labels Check for unused arb file(s) entries
--loc
List items registered in locator but not used
-v, --verbose Enable verbose logging
-h, --help Print help (see a summary with '-h')
Rust has great libraries for creating custom parsers and is really performant. While developing this and testing it against a Flutter project with over 7100 files, it managed to complete it in less than second with all the flags enabled except remove.
It would be possible to do the same in Dart using the Analyzer package, but the performance would be not great.
Contributions, suggestions and PRs are welcome.