Releases: Coding-Dev-Tools/deadcode
Releases · Coding-Dev-Tools/deadcode
v0.1.1 — Bug Fix + Config File + CI Gating
Sorry, something went wrong.
No results found
What's New in v0.1.1
Bug Fix
- Fixed unreferenced component detection: The all_imported_names collection loop was a no-op, causing components that ARE imported to be falsely reported as unreferenced. Now correctly uses imports.keys() to get all imported names.
Features
- .deadcode.yml config file support: Create a config file in your project root to set ignore patterns, enabled categories, and fail threshold — no more repeating CLI flags.
- --fail N option for CI gating: deadcode scan --fail 10 exits with code 1 if findings >= 10. Perfect for CI pipelines. Can also be set via fail_threshold in .deadcode.yml.
- Config + CLI merge: CLI --ignore flags are merged with config file ignore patterns, not replaced.
Docs
- Removed false claim about TypeScript compiler API (DeadCode uses regex-based pattern scanning)
- Documented .deadcode.yml configuration format
- Documented --fail option for CI integration
Tests
- 39/39 passing (23 original + 16 new tests for config, fail threshold, and bug fix)
v0.1.0 - Initial Release
Sorry, something went wrong.
No results found
DeadCode CLI v0.1.0 - Detect unused exports, dead routes, orphaned CSS, and unreferenced components in TS/React/Next.js.
Features: scan, remove (with --dry-run), stats, category filtering, pathspec-based filtering, Rich CLI output.
23/23 tests passing.