rev-dep 2.0.0 → 2.2.0

package/Readme.md

@@ -1,17 +1,18 @@
 <p align="center">
-<img src="https://github.com/jayu/rev-dep/raw/master/logo.png" width="400">
+<img src="https://github.com/jayu/rev-dep/raw/master/logo.png" width="400" alt="Rev-dep logo">
 </p>
+
 <p align="center">
-  <a href="#about-">About</a>&nbsp;&nbsp;•&nbsp;&nbsp;  
-  <a href="#getting-started-">Getting Started</a>&nbsp;&nbsp;•&nbsp;&nbsp; 
-  <a href="#recipes-️">Recipes</a>&nbsp;&nbsp;•&nbsp;&nbsp; 
-  <a href="#cli-reference-">CLI Reference</a> 
+  <a href="#key-features-">Key Features</a>&nbsp;&nbsp;•&nbsp;&nbsp;  
+  <a href="#installation-">Installation</a>&nbsp;&nbsp;•&nbsp;&nbsp; 
+  <a href="#practical-examples-">Practical Examples</a>&nbsp;&nbsp;•&nbsp;&nbsp; 
+  <a href="#cli-reference-">CLI Reference</a>
 </p>
 
 <p align="center">
-  Dependency analysis and optimization toolkit for modern TypeScript projects.
+  Dependency analysis and optimization toolkit for modern JavaScript and TypeScript projects.  
   <br>
-  <a href="#reimplemented-to-achieve-7x-37x-speedup">Completely rewritten in Go for maximum speed and efficiency ⚡</a>
+  Trace imports, find unused code, clean dependencies — all from a blazing-fast CLI.
 </p>
 
 ---
@@ -19,150 +20,196 @@
 <img alt="rev-dep version" src="https://img.shields.io/npm/v/rev-dep"> <img alt="rev-dep license" src="https://img.shields.io/npm/l/rev-dep"> <img alt="rev-dep PRs welcome" src="https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat-square">
 
 
-## About 📣
-
-The tool was created to help with daily development struggles by answering these questions:
 
-👉 What entry points does my codebase have?
+# **About 📣**
 
-👉 Which entry points use a given file?
+Working in large JS/TS projects makes it difficult to answer simple but crucial questions:
 
-👉 Which dependencies does a given file have?
+* Which files depend on this file?
+* Is this file even used?
+* Which files does this entry point import?
+* Do I have circular dependencies?
+* Which packages in node_modules are unused?
+* Which modules take the most disk space?
 
-👉 Do any circular dependencies exist in the project?
+Rev-dep helps you understand the real structure of your codebase so you can debug issues faster, refactor safely, and keep your dependencies clean.
 
-👉 Which node modules are unused or not listed in package.json?
+It's particularly useful for JavaScript projects without TypeScript or test coverage — places where answering question "What will break if I change this" is not straightforward  
 
-👉 Which node modules take up the most space on disk?
 
+## **Why Rev-dep? 🤔**
 
-This helps to debug project dependencies, plan refactoring, optimize bundles or plan code splitting.
+Rev-dep is designed for **fast iteration** and **minimal, actionable results** — no noise, just answers.
 
-It's especially useful in JS world without TypeScript or tests coverage.
+### ✅ **Results in milliseconds**
 
-It also helps to identify and eliminate dead files, understand the complexity of the file dependencies
+Built in Go for speed. Even on large codebases, rev-dep responds almost instantly.
 
-[🦘 Jump to CLI reference](#cli-reference-)
+### ✅ **Actionable, list-based output**
 
-### Use cases 🧑‍💻
+You get **exact file paths**, **import chains**, and **clear dependency relationships** — the kind of information you can fix or clean up right away.
 
-- [You plan to refactor some file and you wonder which entry points are affected](#how-to-identify-where-a-file-is-used-in-the-project)
-- [You are wondering wether a given source file is used](#how-to-check-if-a-file-is-used-in-the-project)
-- [You wonder if there are any dead files in your project](#how-to-identify-dead-files-in-the-project)
-- [You want to verify if a given entry point imports only the required files](#how-to-check-which-files-are-imported-by-a-given-file)
-- [You want to optimize the amount of files imported by an entry point](#how-to-reduce-amount-of-files-imported-by-entry-point)
-- [You want to detect circular dependencies in your project](#how-to-detect-circular-dependencies-in-the-project)
-- [You want to find unused node modules to clean up dependencies](#how-to-find-unused-node-modules)
-- [You want to identify which node modules are consuming the most disk space](#how-to-identify-space-consuming-node-modules)
+### ✅ **Designed for real-world JS/TS**
 
-### How about dependency or bundle graphs?
+Works with mixed JS/TS projects, path aliases and thousands of files without configuration hassles.
 
-There are tool that can output nice, visual representation of project dependencies like [webpack-bundle-analyzer](https://www.npmjs.com/package/webpack-bundle-analyzer) or [dependency-cruiser](https://www.npmjs.com/package/dependency-cruiser) (_which btw rev-dep uses for non-TS codebases_)
+### ✅ **Deep analysis, one CLI**
 
-While graphs can be useful to identify major problems like too big bundle size or to visualize mess in your deps, it's hard to take any action based on them (_at least it was hard for me_ 🤷‍♂️)
+Unused files, unused or missing dependencies, reverse-imports, entry point detection, node_modules insights, dependency paths — everything in one tool.
 
-`rev-dep` visualize dependencies as lists, so it's really easy to see where to cut the line to solve the problem.
 
-## Getting Started 🎉
+### ✅ **Much faster than alternatives**
 
-### Install globally to use as CLI tool
+Rev-dep outperforms Madge, dpdm, dependency-cruiser, skott, knip, depcheck and other similar tools. 
 
-`yarn global add rev-dep`
+For large project with 500k+ lines of code and 6k+ source code files get checks as fast as:
 
-`npm -g install rev-dep`
+| Task | Execution Time [ms] | Alternative | Alternative Time [ms] | Slower Than Rev-dep | 
+|------|-------|--------------|------|----|
+| Find circular dependencies | 289 | dpdm-fast | 7061|  24x|
+| Find unused files | 588 | knip | 6346 | 11x |
+| Find unused node modules | 594 | knip | 6230 | 10x |
+| Find missing node modules | 553 | knip| 6226 | 11x |
+| List all files imported by an entry point | 229 | madge | 4467 | 20x | 
+| Discover entry points | 323 | madge | 67000 | 207x
+| Resolve dependency path between files | 228 | please suggest | 
+| Count lines of code | 342 | please suggest | 
+| Check node_modules disk usage | 1619 | please suggest | 
+| Analyze node_modules directory sizes | 521 | please suggest | 
 
-`pnpm global add rev-dep`
+>Benchmark run on WSL Linux Debian Intel(R) Core(TM) i9-14900KF CPU @ 2.80GHz
 
-## Recipes 🌶️
+# **Key Features 🚀**
 
-### How to identify where a file is used in the project?
+* 🔍 **Reverse dependency lookup** — see all entry points that require a given file
+* 🗂️ **Entry point discovery**
+* 🧹 **Dead file detection**
+* 📦 **Unused / missing / used node modules / dependencies analysis**
+* 🔄 **Circular imports/dependencies detection**
+* 🧭 **Trace all import paths between files**
+* 📁 **List all files imported by any entry point**
+* 📏 **Count actual lines of code (excluding comments and blanks)**
+* 💽 **Node modules disk usage & size analysis**
+* 💡 **Works with both JavaScript and TypeScript**
+* ⚡ **Built for large codebases**
 
-Just use `rev-dep resolve --file path/to/file.ts`
+# **Installation 📦**
 
-You will see all the entry points that implicitly require given file together with resolution path.
+Install globally to use as a CLI tool:
 
-[`resolve` Command CLI reference](#rev-dep-resolve)
+```
+yarn global add rev-dep
+```
 
-#### Getting more details about file resolution in given entry point
+```
+npm install -g rev-dep
+```
 
-To find out all paths combination use `rev-dep resolve` with `-a` flag
+```
+pnpm global add rev-dep
+```
 
-> You might be surprised how complex dependency tree can be!
 
-</details>
+# **Quick Examples ⚡**
 
-### How to check if a file is used in the project?
+A few instant-use examples to get a feel for the tool:
 
-Use `rev-dep resolve --file path/to/file.ts --compact-summary`
+```bash
+# Detect unused node modules
+rev-dep node-modules unused
 
-As a result you will see total amount of entry points requiring a given file.
+# Detect circular imports/dependencies
+rev-dep circular
 
-> Note that among the entry points list there might be some dead files importing the searched file
+# List all entry points in the project
+rev-dep entry-points
 
-[`resolve` Command CLI reference](#rev-dep-resolve)
+# Check which files an entry point imports
+rev-dep files --entry-point src/index.ts
 
-### How to identify dead files in the project?
+# Find every entry point that depends on a file
+rev-dep resolve --file src/utils/math.ts
 
-Use `rev-dep entry-points` to get list of all files that are not required by any other files in the project.
+# Resolve dependency path between files
+rev-dep resolve --file src/utils/math.ts --entry-point src/index.ts
 
-You might want to exclude some file paths that are meant to be actual entry point like `index.js` or `**/pages/**` in `next.js` projects using `--result-exclude` flag. The same for configuration files like `babel.config.js`
+```
 
-Review the list and look for suspicious files like `src/ui/components/SomeComponent/index.js`
+# **Practical Examples 🔧**
 
-[`entry-points` command CLI reference](#rev-dep-entry-points)
 
-### How to check which files are imported by a given file?
+Practical examples show how to use rev-dep commands to build code quality checks for your project.
 
-To get a full list of files imported by given entry point use `rev-dep files --entry-point path/to/file.ts`.
+### **How to identify where a file is used in the project**
 
-You can use `--count` flag if you are interested in the amount.
+```
+rev-dep resolve --file path/to/file.ts
+```
 
-This is a good indicator of how heavy a given entry point or component is
+You’ll see all entry points that implicitly require that file, along with resolution paths.
 
-[`files` command CLI reference](#rev-dep-files)
+### **How to check if a file is used**
 
-### How to reduce amount of files imported by entry point?
+```
+rev-dep resolve --file path/to/file.ts --compact-summary
+```
 
-There is no easy how to for this process, but you can do it iteratively using `rev-dep` commands `files` and `resolve`
+Shows how many entry points indirectly depend on the file.
 
-1. Get the list of files imported by entry-point
+### **How to identify dead files**
 
-   `rev-dep files --entry-point path/to/entry-point`
+```
+rev-dep entry-points
+```
 
-2. Identify some suspicious files on the list, components that should not be used on the given page or not related utility files
-3. Get all resolution paths for a suspicious file
+Exclude framework entry points if needed using `--result-exclude`.
 
-   `rev-dep resolve --file path/to/suspicious-file --entry-points path/to/entry-point --all`
+### **How to list all files imported by an entry point**
 
-4. You would usually find out that there is some file, like directory `index` file that given entry point is using, which is mandatory, but as a side effect it imports a few files that are redundant for your entry point. In most cases you should be able to decouple the imports or reverse the dependency to cut off the resolution path for the unwanted file
+```
+rev-dep files --entry-point path/to/file.ts
+```
 
-### How to detect circular dependencies in the project?
+Useful for identifying heavy components or unintended dependencies.
 
-Use `rev-dep circular` to find all circular dependencies between modules in your project.
+### **How to reduce unnecessary imports for an entry point**
 
-Circular dependencies can cause runtime errors, memory leaks, and make code difficult to understand and maintain. It's important to identify and resolve them early.
+1. List all files imported:
 
-You can use `--ignore-type-imports` flag to exclude type-only imports from the analysis if they're not relevant to your use case.
+   ```
+   rev-dep files --entry-point path/to/entry.ts
+   ```
+2. Identify suspicious files.
+3. Trace why they are included:
 
-[`circular` command CLI reference](#rev-dep-circular)
+   ```
+   rev-dep resolve --file path/to/suspect --entry-points path/to/entry.ts --all
+   ```
 
-### How to find unused node modules?
+### **How to detect circular dependencies**
 
-Use `rev-dep node-modules unused` to identify packages that are installed but not actually imported in your code.
+```
+rev-dep circular
+```
 
-This helps clean up your `package.json` and reduce the size of your `node_modules` directory. You might want to exclude type definitions using `--exclude-modules=@types/*` since they're often used indirectly.
+### **How to find unused node modules**
 
-[`node-modules unused` command CLI reference](#rev-dep-node-modules-unused)
+```
+rev-dep node-modules unused
+```
 
-### How to identify space-consuming node modules?
+### **How to find missing node modules**
 
-Use `rev-dep node-modules dirs-size` to calculate and display the size of `node_modules` directories.
+```
+rev-dep node-modules missing
+```
 
-This helps identify which packages are taking up the most disk space, allowing you to make informed decisions about dependency management or look for lighter alternatives.
+### **How to check node_modules space usage**
 
-For detailed analysis of specific modules, use `rev-dep node-modules analyze-size` with the package names you want to investigate.
+```
+rev-dep node-modules dirs-size
+```
 
-[`node-modules dirs-size` command CLI reference](#rev-dep-node-modules-dirs-size)
 
 ## Reimplemented to achieve 7x-37x speedup
 
@@ -177,7 +224,7 @@ Benchmark was run on TypeScript codebase with 507658 lines of code and 5977 sour
 
 Memory usage on Mac was measure using `/usr/bin/time` utility. Memory usage on Linux was not measured because I could't find reliable way to measure RAM usage on Linux. Subsequent runs had too much fluctuation.
 
-### Mac book Pro M1 256GB, power save off; 
+### MacBook Pro with Apple M1 chip, 16GB of RAM and 256GB of storage. Power save mode off
 
 | Command                                                      | V1 Time | V2 Time | Time Change | V1 RAM | V2 RAM | RAM Change |
 | ------------------------------------------------------------ | ------- | ------- | ----------- | ------ | ------ | ---------- |
@@ -273,9 +320,9 @@ Any other discrepancies between TypeScript module resolution and rev-dep should
 
 - Linux x64
 - MacOS Apple Silicon
+- Windows x64
 
-There are the platforms I use and know. For these I build and tested binaries. 
-Go allows for cross-compiling, so I'm happy to build and distribute binaries for other platforms as well, but I haven't tested it. 
+Go allows for cross-compiling, so I'm happy to build and distribute binaries for other platforms as well.
 Feel free to open an issue if you need support for another platform.
 
 ## CLI reference 📖
@@ -307,8 +354,8 @@ rev-dep circular --ignore-types-imports
   -c, --cwd string             Working directory for the command (default "$PWD")
   -h, --help                   help for circular
   -t, --ignore-type-imports    Exclude type imports from the analysis
-      --package-json string    Path to package.json (default: ./package.json) (default "package.json")
-      --tsconfig-json string   Path to tsconfig.json (default: ./tsconfig.json) (default "tsconfig.json")
+      --package-json string    Path to package.json (default: ./package.json)
+      --tsconfig-json string   Path to tsconfig.json (default: ./tsconfig.json)
 ```
 
 
@@ -339,11 +386,11 @@ rev-dep entry-points --print-deps-count
       --graph-exclude strings    Exclude files matching these glob patterns from analysis
   -h, --help                     help for entry-points
   -t, --ignore-type-imports      Exclude type imports from the analysis
-      --package-json string      Path to package.json (default: ./package.json) (default "package.json")
+      --package-json string      Path to package.json (default: ./package.json)
       --print-deps-count         Show the number of dependencies for each entry point
       --result-exclude strings   Exclude files matching these glob patterns from results
       --result-include strings   Only include files matching these glob patterns in results
-      --tsconfig-json string     Path to tsconfig.json (default: ./tsconfig.json) (default "tsconfig.json")
+      --tsconfig-json string     Path to tsconfig.json (default: ./tsconfig.json)
 ```
 
 
@@ -374,8 +421,8 @@ rev-dep files --entry-point src/index.ts
   -p, --entry-point string     Entry point file to analyze (required)
   -h, --help                   help for files
   -t, --ignore-type-imports    Exclude type imports from the analysis
-      --package-json string    Path to package.json (default: ./package.json) (default "package.json")
-      --tsconfig-json string   Path to tsconfig.json (default: ./tsconfig.json) (default "tsconfig.json")
+      --package-json string    Path to package.json (default: ./package.json)
+      --tsconfig-json string   Path to tsconfig.json (default: ./tsconfig.json)
 ```
 
 
@@ -575,9 +622,9 @@ rev-dep node-modules missing --entry-points=src/main.ts
   -h, --help                               help for missing
   -t, --ignore-type-imports                Exclude type imports from the analysis
   -i, --include-modules strings            list of modules to include in the output
-      --package-json string                Path to package.json (default: ./package.json) (default "package.json")
+      --package-json string                Path to package.json (default: ./package.json)
       --pkg-fields-with-binaries strings   Additional package.json fields to check for binary usages
-      --tsconfig-json string               Path to tsconfig.json (default: ./tsconfig.json) (default "tsconfig.json")
+      --tsconfig-json string               Path to tsconfig.json (default: ./tsconfig.json)
       --zero-exit-code                     Use this flag to always return zero exit code
 ```
 
@@ -613,9 +660,9 @@ rev-dep node-modules unused --exclude-modules=@types/*
   -h, --help                               help for unused
   -t, --ignore-type-imports                Exclude type imports from the analysis
   -i, --include-modules strings            list of modules to include in the output
-      --package-json string                Path to package.json (default: ./package.json) (default "package.json")
+      --package-json string                Path to package.json (default: ./package.json)
       --pkg-fields-with-binaries strings   Additional package.json fields to check for binary usages
-      --tsconfig-json string               Path to tsconfig.json (default: ./tsconfig.json) (default "tsconfig.json")
+      --tsconfig-json string               Path to tsconfig.json (default: ./tsconfig.json)
       --zero-exit-code                     Use this flag to always return zero exit code
 ```
 
@@ -653,9 +700,9 @@ rev-dep node-modules used -p src/index.ts --group-by-module
   -h, --help                               help for used
   -t, --ignore-type-imports                Exclude type imports from the analysis
   -i, --include-modules strings            list of modules to include in the output
-      --package-json string                Path to package.json (default: ./package.json) (default "package.json")
+      --package-json string                Path to package.json (default: ./package.json)
       --pkg-fields-with-binaries strings   Additional package.json fields to check for binary usages
-      --tsconfig-json string               Path to tsconfig.json (default: ./tsconfig.json) (default "tsconfig.json")
+      --tsconfig-json string               Path to tsconfig.json (default: ./tsconfig.json)
 ```
 
 
@@ -689,14 +736,93 @@ rev-dep resolve -p src/index.ts -f src/utils/helpers.ts
       --graph-exclude strings   Glob patterns to exclude files from dependency analysis
   -h, --help                    help for resolve
   -t, --ignore-type-imports     Exclude type imports from the analysis
-      --package-json string     Path to package.json (default: ./package.json) (default "package.json")
-      --tsconfig-json string    Path to tsconfig.json (default: ./tsconfig.json) (default "tsconfig.json")
+      --package-json string     Path to package.json (default: ./package.json)
+      --tsconfig-json string    Path to tsconfig.json (default: ./tsconfig.json)
 ```
 
 
 
 <!-- cli-docs-end -->
 
+## Circular check performance comparison
+
+Benchmark performed on TypeScript codebase with `6034` source code files and `518862` lines of code.
+
+Benchmark performed on MacBook Pro with Apple M1 chip, 16GB of RAM and 256GB of Storage. Power save mode off.
+
+Benchmark performed with `hyperfine` using 8 runs per test and 4 warm up runs, taking mean time values as a result. If single run was taking more than 10s, only 1 run was performed.
+
+`rev-dep` circular check is **12 times** faster than the fastest alternative❗
+
+| Tool | Version | Command to Run Circular Check | Time |
+|------|---------|-------------------------------|------|
+| 🥇 [rev-dep](https://github.com/jayu/rev-dep) | 2.0.0 | `rev-dep circular` | 397 ms |
+| 🥈 [dpdm-fast](https://github.com/SunSince90/dpdm-fast) | 1.0.14 | `dpdm --no-tree --no-progress  --no-warning` + list of directories with source code  | 4960 ms |
+| 🥉 [dpdm](https://github.com/acrazing/dpdm) | 3.14.0 | `dpdm  --no-warning` + list of directories with source code | 5030 ms |
+| [skott](https://github.com/antoine-coulon/skott) | 0.35.6 | node skoscript using `findCircularDependencies` function  | 29575 ms |
+| [madge](https://github.com/pahen/madge) | 8.0.0 | `madge --circular --extensions js,ts,jsx,tsx .` | 69328 ms |
+| [circular-dependency-scanner](https://github.com/emosheeep/circular-dependency-scanner) | 2.3.0 | `ds` - out of memory error | n/a |
+
+## Glossary
+
+Some of the terms used in the problem space that **rev-dep** covers can be confusing.
+Here is a small glossary to help you navigate the concepts.
+
+### Dependency
+
+A *dependency* can be understood literally. In the context of a project’s dependency graph, it may refer to:
+
+* a **node module / package** (a package is a dependency of a project or file), or
+* a **source code file** (a file is a dependency of another file if it imports it).
+
+### Entry point
+
+An *entry point* is a source file that is **not imported by any other file**.
+It can represent:
+
+* the main entry of the application
+* an individual page or feature
+* configuration or test bootstrap files
+
+— depending on the project structure.
+
+### Unused / Dead file
+
+A file is considered *unused* or *dead* when:
+
+* it is an **entry point** (nothing imports it), **and**
+* running it does **not produce any meaningful output** or side effect.
+
+In practice, such files can often be removed safely.
+
+### Circular dependency
+
+A *circular dependency* occurs when a file **directly or indirectly imports itself** through a chain of imports.
+
+This can lead to unpredictable runtime behavior, uninitialized values, or subtle bugs.
+However, circular dependencies between **TypeScript type-only imports** are usually harmless.
+
+### Reverse dependency (or "dependents")
+
+Files that *import* a given file.
+Useful for answering: "What breaks if I change or delete this file?"
+
+### Import graph / Dependency graph
+
+A visual representation of how files or modules import each other.
+
+### Missing dependency / unused node module
+
+A module that your code imports but is **not listed in package.json**.
+
+### Unused dependency / unused node module
+
+A dependency listed in **package.json** that is **never imported** in the source code.
+
+### Root directory / Project root
+
+The top-level directory used as the starting point for dependency analysis.
+
 ## Made in 🇵🇱 and 🇯🇵 with 🧠 by [@jayu](https://github.com/jayu)
 
 I hope that this small piece of software will help you discover and understood complexity of your project hence make you more confident while refactoring. If this tool was useful, don't hesitate to give it a ⭐!

package/bin.js

@@ -11,6 +11,7 @@ const nestedNodeModulesPath = path.join(__dirname, 'node_modules', binaryPackage
 const siblingNodeModulesPath = path.join(__dirname, '../', binaryPackageName)
 
 const checkedPaths = []
+const fsRoot = path.parse(__dirname).root
 
 if (fs.existsSync(nestedNodeModulesPath)) {
   packageDir = nestedNodeModulesPath
@@ -27,7 +28,7 @@ else if (fs.existsSync(siblingNodeModulesPath)) {
     }
     else {
       checkedPaths.push(pathToCheck)
-      if (lookupDir === '/') {
+      if (lookupDir === fsRoot) {
         lookupDir = undefined
       }
       else {
@@ -41,6 +42,7 @@ if (packageDir === '') {
   console.error("Could not locate rev-dep binary for your platform: ", binaryPackageName)
   console.log('Checked paths', checkedPaths)
   console.log('Please open an issue to request platform support')
+  console.log('https://github.com/jayu/rev-dep/issues')
   process.exit(1)
 }
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "rev-dep",
-  "version": "2.0.0",
-  "description": "Dependency debugging tool for JavaScript and TypeScript projects",
+  "version": "2.2.0",
+  "description": "Trace imports, detect unused code, clean dependencies — all with a super-fast CLI",
   "bin": "bin.js",
   "files": [
     "bin.js"
@@ -17,28 +17,31 @@
     "node": ">=18"
   },
   "optionalDependencies": {
-    "@rev-dep/darwin-arm64": "2.0.0",
-    "@rev-dep/linux-x64": "2.0.0"
+    "@rev-dep/darwin-arm64": "2.2.0",
+    "@rev-dep/linux-x64": "2.2.0",
+    "@rev-dep/win32-x64": "2.2.0"
   },
   "keywords": [
-    "dependencies",
-    "deps",
-    "dependency graph",
-    "dependency debugging",
-    "entry points",
-    "dependency resolution",
-    "reverse dependency resolution",
-    "import path",
-    "resolution path",
-    "dependency optimization",
-    "dependency analysis",
-    "bundle",
-    "dependency tree",
-    "imports",
-    "dependencies checking",
-    "imports debugging",
-    "imports analysis",
-    "imports search",
-    "file dependencies"
+    "dependency-analysis",
+    "reverse-dependencies",
+    "dependency-resolution",
+    "file-dependencies",
+    "unused-files",
+    "dead-files",
+    "unused-dependencies",
+    "missing-dependencies",
+    "used-dependencies",
+    "module-analysis",
+    "import-analysis",
+    "entry-point-analysis",
+    "dependency-path",
+    "circular-dependency-detection",
+    "node-modules-analysis",
+    "module-size-analysis",
+    "lines-of-code",
+    "project-audit",
+    "typescript-analysis",
+    "javascript-analysis",
+    "monorepo-analysis"
   ]
 }