npm - rev-dep - Versions diffs - 2.6.1 → 2.7.1 - Mend

rev-dep 2.6.1 → 2.7.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (2) hide show

package/Readme.md +434 -416
package/package.json +4 -4

package/Readme.md CHANGED Viewed

@@ -3,100 +3,115 @@
 </p>
 <p align="center">
-  <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="#capabilities-">Capabilities</a>&nbsp;&nbsp;•&nbsp;&nbsp;
+  <a href="#installation-">Installation</a>&nbsp;&nbsp;•&nbsp;&nbsp;
+  <a href="#exploratory-toolkit-">Exploratory Toolkit</a>&nbsp;&nbsp;•&nbsp;&nbsp;
   <a href="#cli-reference-">CLI Reference</a>
 </p>
 <p align="center">
-  Dependency analysis and optimization toolkit for modern JavaScript and TypeScript projects.
+  Dependency analysis and optimization toolkit for modern JavaScript and TypeScript codebases.
   <br>
-  Trace imports, identify circular dependencies, find unused code, clean node modules — all from a blazing-fast CLI.
+  Enforce dependency graph hygiene and remove unused bits with a very fast CLI.
+</p>
+<p align="center">
+<img src="https://github.com/jayu/rev-dep/raw/master/demo.png" alt="Rev-dep config execution CLI output"width="400">
 </p>
 ---
 <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 📣**
+As codebases scale, maintaining a mental map of dependencies becomes impossible. **Rev-dep** is a high-speed governance engine designed to enforce architecture integrity and dependency hygiene across large-scale JS/TS projects.
-# **About 📣**
+<p align="center"><b>Think of Rev-dep as a high-speed linter for your dependency graph.</b></p>
-Working in large JS/TS projects makes it difficult to answer simple but crucial questions:
+**Consolidate fragmented, sequential checks from multiple slow tools into a single, high-performance engine.** Rev-dep executes a full suite of governance checks—including circularity, orphans, module boundaries and more, in one parallelized pass. Implemented in **Go** to bypass the performance bottlenecks of Node-based analysis, it can audit a **500k+ LoC project in approximately 500ms**.
-* 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?
+### **Automated Codebase Governance**
-Rev-dep helps you understand the real structure of your codebase so you can debug issues faster, refactor safely, and keep your dependencies clean.
+Rev-dep moves beyond passive scanning to active enforcement, answering (and failing CI for) the hard questions:
-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
+* **Architecture Integrity:** "Is my 'Domain A' illegally importing from 'Domain B'?".
+* **Dead Code & Bloat:** "Are these files unreachable, or are these `node_modules` unused?".
+* **Refactoring Safety:** "Which entry points actually use this utility, and are there circular chains?".
+* **Workspace Hygiene:** "Are my imports consistent and are all dependencies declared?".
+Rev-dep serves as a **high-speed gatekeeper** for your CI, ensuring your dependency graph remains lean and your architecture stays intact as you iterate.
 ## **Why Rev-dep? 🤔**
-Rev-dep is designed for **fast iteration** and **minimal, actionable results** — no noise, just answers.
+### 🏗️ **First-class monorepo support**
+Designed for modern workspaces (`pnpm`, `yarn`, `npm`). Rev-dep natively resolves `package.json` **exports/imports** maps, TypeScript aliases and traces dependencies across package boundaries.
-### ✅ **Results in milliseconds**
+### 🛡️ **Config-Based Codebase Governance**
+Move beyond passive scanning. Use the configuration engine to enforce **Module Boundaries** and **Import Conventions**. Execute a full suite of hygiene checks (circularity, orphans, unused modules and more) in a **single, parallelized pass** that serves as a high-speed gatekeeper for your CI.
-Built in Go for speed. Even on large codebases, rev-dep responds almost instantly.
+### 🔍 **Exploratory Toolkit**
+CLI toolkit that helps debug issues with dependencies between files. Understand transitive relation between files and fix issues.
-### ✅ **Actionable, list-based output**
+### ⚡ **Built for Speed and CI Efficiency**
+Implemented in **Go** to eliminate the performance tax of Node-based analysis. By processing files in parallel, Rev-dep offers **10x-200x faster execution** than alternatives, significantly **reducing CI costs** and developer wait-states.
-You get **exact file paths**, **import chains**, and **clear dependency relationships** — the kind of information you can fix or clean up right away.
+> **Rev-dep can audit a 500k+ LoC project in around 500ms.**
+> [See the performance comparison](#performance-comparison-)
-### ✅ **Designed for real-world JS/TS with first class monorepo support**
+## Capabilities 🚀
-Works with mixed JS/TS projects, path aliases and thousands of files without configuration hassles.
+## Governance and maintenance (config-based) 🛡️
-### ✅ **Deep analysis, one CLI**
+Use `rev-dep config run` to execute multiple checks in one pass for all packages.
-Unused files, unused or missing dependencies, reverse-imports, entry point detection, node_modules insights, dependency paths — everything in one tool.
+Available checks:
+- `moduleBoundaries` - enforce architecture boundaries between modules.
+- `importConventions` - enforce import style conventions (offers autofix).
+- `unusedExportsDetection` - detect exports that are never used (offers autofix).
+- `orphanFilesDetection` - detect dead/orphan files (offers autofix).
+- `unusedNodeModulesDetection` - detect dependencies declared but not used.
+- `missingNodeModulesDetection` - detect imports missing from package json.
+- `unresolvedImportsDetection` - detect unresolved import requests.
+- `circularImportsDetection` - detect circular imports.
-### ✅ **Much faster than alternatives**
+## Exploratory analysis (CLI-based) 🔍
-Rev-dep outperforms Madge, dpdm, dependency-cruiser, skott, knip, depcheck and other similar tools.
+Use CLI commands for ad-hoc dependency exploration:
-For large project with 500k+ lines of code and 6k+ source code files get checks as fast as:
+- `entry-points` - discover project entry points.
+- `files` - list dependency tree files for a given entry point.
+- `resolve` - trace dependency paths between files (who imports this file).
+- `imported-by` - list direct importers of a file.
+- `circular` - list circular dependency chains.
+- `node-modules` - inspect `used`, `unused`, `missing`, and `installed` node modules.
+- `lines-of-code` - count effective LOC.
+- `list-cwd-files` - list all source code files in CWD
-| 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 |
+## **Installation 📦**
->Benchmark run on WSL Linux Debian Intel(R) Core(TM) i9-14900KF CPU @ 2.80GHz
+**Install locally to set up project check scripts**
-# **Key Features 🚀**
+```
+yarn add -D rev-dep
+```
-* 🔍 **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 and monorepos**
-* 🏗️ **Supports TypeScript path aliases and package.json imports and exports map**
+```
+npm install -D rev-dep
+```
-# **Installation 📦**
+```
+pnpm add -D rev-dep
+```
-Install globally to use as a CLI tool:
+Create config file for a quick start:
+```
+npx rev-dep config init
+```
+**Install globally to use as a CLI tool:**
 ```
 yarn global add rev-dep
@@ -110,8 +125,7 @@ npm install -g rev-dep
 pnpm global add rev-dep
 ```
-# **Quick Examples ⚡**
+## **Quick Examples 💡**
 A few instant-use examples to get a feel for the tool:
@@ -136,178 +150,20 @@ rev-dep resolve --file src/utils/math.ts --entry-point src/index.ts
 ```
-# **Practical Examples 🔧**
-Practical examples show how to use rev-dep commands to build code quality checks for your project.
-### **How to identify where a file is used in the project**
-```
-rev-dep resolve --file path/to/file.ts
-```
-You’ll see all entry points that implicitly require that file, along with resolution paths.
-### **How to check if a file is used**
-```
-rev-dep resolve --file path/to/file.ts --compact-summary
-```
-Shows how many entry points indirectly depend on the file.
-### **How to identify dead files**
-```
-rev-dep entry-points
-```
-Exclude framework entry points if needed using `--result-exclude`.
-For example exclude Next.js valid entry points when using pages router, exclude scripts directory - scripts are valid entry-points and exclude all test files:
-```
-rev-dep entry-points --result-exclude "pages/**","scripts/**","**/*.test.*"
-```
-### **How to list all files imported by an entry point**
-```
-rev-dep files --entry-point path/to/file.ts
-```
-Useful for identifying heavy components or unintended dependencies.
-### **How to reduce unnecessary imports for an entry point**
-1. List all files imported:
-   ```
-   rev-dep files --entry-point path/to/entry.ts
-   ```
-2. Identify suspicious files.
-3. Trace why they are included:
-   ```
-   rev-dep resolve --file path/to/suspect --entry-points path/to/entry.ts --all
-   ```
-### **How to detect circular dependencies**
-```
-rev-dep circular
-```
-### **How to find unused node modules**
-```
-rev-dep node-modules unused
-```
-### **How to find missing node modules**
-```
-rev-dep node-modules missing
-```
-### **How to check node_modules space usage**
-```
-rev-dep node-modules dirs-size
-```
-## Working with Monorepo
-Rev-dep provides first-class support for monorepo projects, enabling accurate dependency analysis across workspace packages.
-### followMonorepoPackages Flag
-The `--follow-monorepo-packages` flag enables resolution of imports from monorepo workspace packages. By default, this flag is set to `false` to maintain compatibility with single-package projects.
-```bash
-# Enable monorepo package resolution
-rev-dep circular --follow-monorepo-packages
-rev-dep resolve --file src/utils.ts --follow-monorepo-packages
-rev-dep entry-points --follow-monorepo-packages
-```
-When enabled, rev-dep will:
-- **Detect workspace packages** automatically by scanning for monorepo configuration
-- **Resolve imports between packages** within the workspace
-- **Follow package.json exports** for proper module resolution
-### Exports Map Support
-Rev-dep fully supports the `exports` field in package.json files, which is the standard way to define package entry points in modern Node.js projects.
-The exports map support includes:
-- **Conditional exports** using conditions like `node`, `import`, `default`, and custom conditions
-- **Wildcard patterns** for flexible subpath mapping
-- **Sugar syntax** for simple main export definitions
-- **Nested conditions** for complex resolution scenarios
-### Condition Names Flag
-To control which conditional exports are resolved, use the `--condition-names` flag. This allows you to specify the priority of conditions when resolving package exports:
-```bash
-# Resolve exports for different environments
-rev-dep circular --condition-names=node,import,default
-rev-dep resolve --file src/utils.ts --condition-names=import,node
-rev-dep entry-points --condition-names=default,node,import
-```
-The conditions are processed in the order specified, with the first matching condition being used. Common conditions include:
-- `node` - Node.js environment
-- `import` - ES modules
-- `require` - CommonJS
-- `default` - Fallback condition
-- Custom conditions specific to your project or build tools
-Example package.json with exports:
-```json
-{
-  "name": "@myorg/utils",
-  "exports": {
-    ".": {
-      "import": "./dist/index.mjs",
-      "require": "./dist/index.js",
-      "default": "./dist/index.js"
-    },
-    "./helpers": "./dist/helpers.js",
-    "./types/*": "./dist/types/*.d.ts"
-  }
-}
-```
-### How It Works
-1. **Monorepo Detection**: When `followMonorepoPackages` is enabled, rev-dep scans for workspace configuration (pnpm-workspace.yaml, package.json workspaces, etc.)
-2. **Package Resolution**: Imports to workspace packages are resolved using the package's exports configuration, falling back to main/module fields when exports are not defined
-3. **Dependency Validation**: The tool validates that cross-package imports are only allowed when the target package is listed in the consumer's dependencies or devDependencies
-4. **Path Resolution**: All paths are resolved relative to their respective package roots, ensuring accurate dependency tracking across the entire monorepo
-This makes rev-dep particularly effective for large-scale monorepo projects where understanding cross-package dependencies is crucial for maintaining code quality and architecture.
-## Config-Based Checks
+## Config-Based Checks 🛡️
 Rev-dep provides a configuration system for orchestrating project checks. The config approach is **designed for speed** and is the **preferred way** of implementing project checks because it can execute all checks in a single pass, significantly faster than multiple running individual commands separately.
 Available checks are:
-- **module boundaries** - check if imports respect module boundaries
-- **import conventions** - enforce syntactic consistency for imports (includes autofix capability)
-- **circular imports** - check if there are circular imports
-- **orphan files** - check if there are orphan/dead files
-- **unused node modules** - check against unused node modules
-- **missing node modules** - check against missing node modules
+- `moduleBoundaries` - enforce architecture boundaries between modules.
+- `importConventions` - enforce import style conventions (offers autofix).
+- `unusedExportsDetection` - detect exports that are never used (offers autofix).
+- `orphanFilesDetection` - detect dead/orphan files (offers autofix).
+- `unusedNodeModulesDetection` - detect dependencies declared but not used.
+- `missingNodeModulesDetection` - detect imports missing from package json.
+- `unresolvedImportsDetection` - detect unresolved import requests.
+- `circularImportsDetection` - detect circular imports.
 Checks are grouped in rules. You can have multiple rules, eg. for each monorepo package.
@@ -325,7 +181,7 @@ Behavior of `rev-dep config init`:
 - Monorepo root: Running `rev-dep config init` at the workspace root creates a root rule and a rule for each discovered workspace package.
 - Monorepo workspace package or regular projects: Running `rev-dep config init` inside a directory creates config with a single rule with `path: "."` for this directory.
-Run all configured checks:
+Run all configured checks (dry run, not fixes applied yet):
 ```bash
 # Execute all rules and checks defined in the config
@@ -349,12 +205,44 @@ rev-dep config run --fix
 The configuration file (`rev-dep.config.json(c)` or `.rev-dep.config.json(c)`) allows you to define multiple rules, each targeting different parts of your codebase with specific checks enabled.
+#### Quick Start Configuration
+```jsonc
+{
+  "configVersion": "1.3",
+  "$schema": "https://github.com/jayu/rev-dep/blob/master/config-schema/1.3.schema.json?raw=true",
+  "rules": [
+    {
+      "path": ".",
+      "unusedExportsDetection": {
+        "enabled": true,
+        "autofix": true,
+        "validEntryPoints": ["src/index.ts" ]
+      },
+      "orphanFilesDetection": {
+        "enabled": true,
+        "autofix": true,
+        "validEntryPoints": ["src/index.ts"]
+      },
+      "unusedNodeModulesDetection": {
+        "enabled": true
+      },
+      "circularImportsDetection": {
+        "enabled": true
+      },
+    }
+  ]
+}
+```
+#### Comprehensive Config Example
 Here's a comprehensive example showing all available properties:
 ```jsonc
 {
-  "configVersion": "1.2",
-  "$schema": "https://github.com/jayu/rev-dep/blob/master/config-schema/1.2.schema.json?raw=true", // enables json autocompletion
+  "configVersion": "1.3",
+  "$schema": "https://github.com/jayu/rev-dep/blob/master/config-schema/1.3.schema.json?raw=true", // enables json autocompletion
   "conditionNames": ["import", "default"],
   "ignoreFiles": ["**/*.test.*"],
   "rules": [
@@ -401,7 +289,8 @@ Here's a comprehensive example showing all available properties:
         "enabled": true,
         "validEntryPoints": ["src/index.ts", "src/app.ts"],
         "ignoreTypeImports": true,
-        "graphExclude": ["**/*.test.*", "**/stories/**/*"]
+        "graphExclude": ["**/*.test.*", "**/stories/**/*"],
+        "autofix": true
       },
       "unusedNodeModulesDetection": {
         "enabled": true,
@@ -417,6 +306,21 @@ Here's a comprehensive example showing all available properties:
         "includeModules": ["lodash", "axios"],
         "excludeModules": ["@types/**"],
         "outputType": "groupByFile"
+      },
+      "unusedExportsDetection": {
+        "enabled": true,
+        "validEntryPoints": ["src/index.ts"],
+        "ignoreTypeExports": true,
+        "graphExclude": ["**/*.stories.tsx"],
+        "autofix": true
+      },
+      "unresolvedImportsDetection": {
+        "enabled": true,
+        "ignore": {
+          "src/index.ts": "legacy-unresolved-module"
+        },
+        "ignoreFiles": ["**/*.generated.ts"],
+        "ignoreImports": ["@internal/dev-only"]
       }
     }
   ]
@@ -442,6 +346,8 @@ Each rule can contain the following properties:
 - **`orphanFilesDetection`** (optional): Orphan files detection configuration
 - **`unusedNodeModulesDetection`** (optional): Unused node modules detection configuration
 - **`missingNodeModulesDetection`** (optional): Missing node modules detection configuration
+- **`unusedExportsDetection`** (optional): Unused exports detection configuration
+- **`unresolvedImportsDetection`** (optional): Unresolved imports detection configuration
 - **`importConventions`** (optional): Array of import convention rules
 #### Module Boundary Properties
@@ -469,6 +375,7 @@ Each rule can contain the following properties:
 - **`validEntryPoints`** (optional): Array of valid entry point patterns (eg. ["src/index.ts", "src/main.ts"])
 - **`ignoreTypeImports`** (optional): Exclude type-only imports when building graph (default: false)
 - **`graphExclude`** (optional): File patterns to exclude from graph analysis
+- **`autofix`** (optional): Delete detected orphan files automatically when running `rev-dep config run --fix` (default: false)
 **UnusedNodeModulesDetection:**
 - **`enabled`** (required): Enable/disable unused modules detection
@@ -483,7 +390,19 @@ Each rule can contain the following properties:
 - **`enabled`** (required): Enable/disable missing modules detection
 - **`includeModules`** (optional): Module patterns to include in analysis
 - **`excludeModules`** (optional): Module patterns to exclude from analysis
-- **`outputType`** (optional): Output format - "list", "groupByModule", "groupByFile"
+- **`outputType`** (optional): Output format - "list", "groupByModule", "groupByFile", "groupByModuleFilesCount"
+**UnusedExportsDetection:**
+- **`enabled`** (required): Enable/disable unused exports detection
+- **`validEntryPoints`** (optional): Glob patterns for files whose exports are never reported as unused (eg. ["index.ts", "src/public-api.ts"])
+- **`ignoreTypeExports`** (optional): Skip `export type` / `export interface` from analysis (default: false)
+- **`graphExclude`** (optional): File patterns to exclude from unused exports analysis
+**UnresolvedImportsDetection:**
+- **`enabled`** (required): Enable/disable unresolved imports detection
+- **`ignore`** (optional): Map of file path (relative to rule path directory) to exact import request to suppress
+- **`ignoreFiles`** (optional): File path globs; all unresolved imports from matching files are suppressed
+- **`ignoreImports`** (optional): Import requests to suppress globally in unresolved results
 ### Performance Benefits
@@ -496,92 +415,206 @@ The configuration approach provides significant performance advantages:
 This makes config-based checks faster than running individual commands sequentially, especially for large codebases with multiple sub packages.
+## **Exploratory Toolkit 🔧**
+Practical examples show how to use rev-dep CLI commands to explore, debug or build code quality checks for your project.
-## Reimplemented to achieve 7x-37x speedup
+### **How to identify where a file is used in the project**
-Rev-dep@2.0.0 was reimplemented in Go from scratch to leverage it's concurrency features and better memory management of compiled languages.
+```
+rev-dep resolve --file path/to/file.ts
+```
-As a result v2 is up to 37x faster than v1 and consumes up to 13x less memory.
+You’ll see all entry points that implicitly require that file, along with resolution paths.
-### Performance comparison
+### **How to check if a file is used**
-To compare performance rev-dep was benchmarked with hyperfine using 8 runs per test, taking mean time values as a result.
-Benchmark was run on TypeScript codebase with 507658 lines of code and 5977 source code files.
+```
+rev-dep resolve --file path/to/file.ts --compact-summary
+```
+Shows how many entry points indirectly depend on the file.
-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.
+### **How to identify dead files**
-### MacBook Pro with Apple M1 chip, 16GB of RAM and 256GB of storage. Power save mode off
+```
+rev-dep entry-points
+```
-| Command                                                      | V1 Time | V2 Time | Time Change | V1 RAM | V2 RAM | RAM Change |
-| ------------------------------------------------------------ | ------- | ------- | ----------- | ------ | ------ | ---------- |
-| List entry-points `rev-dep entry-points`                     | 6500ms  | 347ms   | 19x         | ~680MB | ~51MB  | 13x        |
-| List entry-points with dependent files count `-pdc`          | 8333ms  | 782ms   | 11x         | ~885MB | ~110MB | 8x         |
-| List entry-point files `rev-dep files`                       | 2729ms  | 400ms   | 7x          | ~330MB | ~36MB  | 9x         |
-| Resolve dependency path `rev-dep resolve`                    | 2984ms  | 359ms   | 8x          | ~330MB | ~35MB  | 9x         |
+Exclude framework entry points if needed using `--result-exclude`.
-### WSL Linux Debian Intel(R) Core(TM) i9-14900KF CPU @ 2.80GHz
+For example exclude Next.js valid entry points when using pages router, exclude scripts directory - scripts are valid entry-points and exclude all test files:
-| Command                                                                 | V1 Time | V2 Time | Time Change |
-| ----------------------------------------------------------------------- | ------- | ------- | ----------- |
-| List entry-points `rev-dep entry-points`                                | 9904ms  | 270ms   | 37x         |
-| List entry-points with dependent files count `--print-deps-count`       | 10562ms | 458ms   | 23x         |
-| List entry-point files `rev-dep files`                                  | 3097ms  | 230ms   | 13x         |
-| Resolve dependency path `rev-dep resolve`                               | 3146ms  | 230ms   | 14x         |
+```
+rev-dep entry-points --result-exclude "pages/**","scripts/**","**/*.test.*"
+```
-### New features
+### **How to list all files imported by an entry point**
-V2 comes with bunch of new commands
+```
+rev-dep files --entry-point path/to/file.ts
+```
-- `circular` - detects circular dependencies in the project
-- `lines-of-code` - counts actual lines of code in the project excluding comments and blank lines
-- `list-cwd-files` - lists all files in the current working directory
-- `node-modules used` - lists all used node modules
-- `node-modules unused` - lists all unused node modules
-- `node-modules missing` - lists all missing node modules
-- `node-modules installed` - lists all installed node modules
-- `node-modules installed-duplicates` - lists all installed node modules that exist in file system with the same version multiple times
-- `node-modules analyze-size` - analyzes size of specific node modules and helps to identify space-hogging dependencies
-- `node-modules dirs-size` - calculates cumulative files size in node_modules directories
+Useful for identifying heavy components or unintended dependencies.
-### ⚠️ What's not supported
+### **How to reduce unnecessary imports for an entry point**
-Comparing to previous versions, these tsconfig features are not supported
+1. List all files imported:
-#### Multiple path aliases
+   ```
+   rev-dep files --entry-point path/to/entry.ts
+   ```
+2. Identify suspicious files.
+3. Trace why they are included:
-Only first path will be used in resolution.
+   ```
+   rev-dep resolve --file path/to/suspect --entry-points path/to/entry.ts --all
+   ```
+### **How to detect circular dependencies**
+```
+rev-dep circular
+```
+### **How to find unused node modules**
+```
+rev-dep node-modules unused
+```
+### **How to find missing node modules**
+```
+rev-dep node-modules missing
+```
+### **How to check node_modules space usage**
+```
+rev-dep node-modules dirs-size
+```
+## Working with Monorepo 🏗️
+Rev-dep provides first-class support for monorepo projects, enabling accurate dependency analysis across workspace packages.
+### followMonorepoPackages Flag
+The `--follow-monorepo-packages` flag enables resolution of imports from monorepo workspace packages. By default, this flag is set to `false` to maintain compatibility with single-package projects.
+```bash
+# Enable monorepo package resolution
+rev-dep circular --follow-monorepo-packages
+rev-dep resolve --file src/utils.ts --follow-monorepo-packages
+rev-dep entry-points --follow-monorepo-packages
+```
+When enabled, rev-dep will:
+- **Detect workspace packages** automatically by scanning for monorepo configuration
+- **Resolve imports between packages** within the workspace
+- **Follow package.json exports** for proper module resolution
+### Exports Map Support
+Rev-dep fully supports the `exports` field in package.json files, which is the standard way to define package entry points in modern Node.js projects.
+The exports map support includes:
+- **Conditional exports** using conditions like `node`, `import`, `default`, and custom conditions
+- **Wildcard patterns** for flexible subpath mapping
+- **Sugar syntax** for simple main export definitions
+- **Nested conditions** for complex resolution scenarios
+### Condition Names Flag
+To control which conditional exports are resolved, use the `--condition-names` flag. This allows you to specify the priority of conditions when resolving package exports:
+```bash
+# Resolve exports for different environments
+rev-dep circular --condition-names=node,import,default
+rev-dep resolve --file src/utils.ts --condition-names=import,node
+rev-dep entry-points --condition-names=default,node,import
+```
+The conditions are processed in the order specified, with the first matching condition being used. Common conditions include:
+- `node` - Node.js environment
+- `import` - ES modules
+- `require` - CommonJS
+- `default` - Fallback condition
+- Custom conditions specific to your project or build tools
+Example package.json with exports:
 ```json
-// tsconfig.json
 {
-  "paths": {
-    "@/components": ["src/components/*", "src/components2/*"]
+  "name": "@myorg/utils",
+  "exports": {
+    ".": {
+      "import": "./dist/index.mjs",
+      "require": "./dist/index.js",
+      "default": "./dist/index.js"
+    },
+    "./helpers": "./dist/helpers.js",
+    "./types/*": "./dist/types/*.d.ts"
   }
 }
 ```
-Imports that should resolve to `src/components2/*` will be considered unresolved.
+### How It Works
+1. **Monorepo Detection**: When `followMonorepoPackages` is enabled, rev-dep scans for workspace configuration (pnpm-workspace.yaml, package.json workspaces, etc.)
+2. **Package Resolution**: Imports to workspace packages are resolved using the package's exports configuration, falling back to main/module fields when exports are not defined
+3. **Dependency Validation**: The tool validates that cross-package imports are only allowed when the target package is listed in the consumer's dependencies or devDependencies
+4. **Path Resolution**: All paths are resolved relative to their respective package roots, ensuring accurate dependency tracking across the entire monorepo
+This makes rev-dep particularly effective for large-scale monorepo projects where understanding cross-package dependencies is crucial for maintaining code quality and architecture.
+## Performance comparison ⚡
+Rev-dep can perform multiple checks on 500k+ LoC monorepo with several sub-packages in around 500ms.
+It outperforms Madge, dpdm, dependency-cruiser, skott, knip, depcheck and other similar tools.
+Here is a performance comparison of specific tasks between rev-dep and alternatives:
+| 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 |
+>Benchmark run on WSL Linux Debian Intel(R) Core(TM) i9-14900KF CPU @ 2.80GHz
-Why it's not supported? I consider this typescript capability as an anti-pattern. It introduces unnecessary ambiguity in module resolution.
-Implementing this would make code more complex, less maintainable and slower.
+### Circular check performance comparison
-#### Using rev-dep as node module
+Benchmark performed on TypeScript codebase with `6034` source code files and `518862` lines of code.
-Importing rev-dep in JS/TS is no longer supported. Preferred way is to run rev-dep using child process.
+Benchmark performed on MacBook Pro with Apple M1 chip, 16GB of RAM and 256GB of Storage. Power save mode off.
-#### Other discrepancies
+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.
-Any other discrepancies between TypeScript module resolution and rev-dep should be considered as a bug.
+`rev-dep` circular check is **12 times** faster than the fastest alternative❗
-### Supported Platforms
+| 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 script using skott `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 |
-- Linux x64
-- MacOS Apple Silicon
-- Windows x64
-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 📖
@@ -609,14 +642,14 @@ rev-dep circular --ignore-types-imports
 #### Options
 ```
-      --condition-names strings    List of conditions for package.json imports resolution (e.g. node, imports, default)
-  -c, --cwd string                 Working directory for the command (default "$PWD")
-      --follow-monorepo-packages   Enable resolution of imports from monorepo workspace packages
-  -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)
-      --tsconfig-json string       Path to tsconfig.json (default: ./tsconfig.json)
-  -v, --verbose                    Show warnings and verbose output
+      --condition-names strings                                     List of conditions for package.json imports resolution (e.g. node, imports, default)
+  -c, --cwd string                                                  Working directory for the command (default "$PWD")
+      --follow-monorepo-packages strings                            Enable resolution of imports from monorepo workspace packages. Pass without value to follow all, or pass package names
+  -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)
+      --tsconfig-json string                                        Path to tsconfig.json (default: ./tsconfig.json)
+  -v, --verbose                                                     Show warnings and verbose output
 ```
@@ -651,15 +684,16 @@ rev-dep config run [flags]
 #### Options
 ```
-      --condition-names strings    List of conditions for package.json imports resolution (e.g. node, imports, default)
-  -c, --cwd string                 Working directory (default "$PWD")
-      --fix                        Automatically fix fixable issues
-      --follow-monorepo-packages   Enable resolution of imports from monorepo workspace packages
-  -h, --help                       help for run
-      --list-all-issues            List all issues instead of limiting output
-      --package-json string        Path to package.json (default: ./package.json)
-      --tsconfig-json string       Path to tsconfig.json (default: ./tsconfig.json)
-  -v, --verbose                    Show warnings and verbose output
+      --condition-names strings                                     List of conditions for package.json imports resolution (e.g. node, imports, default)
+  -c, --cwd string                                                  Working directory (default "$PWD")
+      --fix                                                         Automatically fix fixable issues
+      --follow-monorepo-packages strings                            Enable resolution of imports from monorepo workspace packages. Pass without value to follow all, or pass package names
+  -h, --help                                                        help for run
+      --list-all-issues                                             List all issues instead of limiting output
+      --package-json string                                         Path to package.json (default: ./package.json)
+      --rules strings                                               Subset of rules to run (comma-separated list of rule paths)
+      --tsconfig-json string                                        Path to tsconfig.json (default: ./tsconfig.json)
+  -v, --verbose                                                     Show warnings and verbose output
 ```
@@ -705,19 +739,19 @@ rev-dep entry-points --print-deps-count
 #### Options
 ```
-      --condition-names strings    List of conditions for package.json imports resolution (e.g. node, imports, default)
-  -n, --count                      Only display the number of entry points found
-  -c, --cwd string                 Working directory for the command (default "$PWD")
-      --follow-monorepo-packages   Enable resolution of imports from monorepo workspace packages
-      --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)
-      --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)
-  -v, --verbose                    Show warnings and verbose output
+      --condition-names strings                                     List of conditions for package.json imports resolution (e.g. node, imports, default)
+  -n, --count                                                       Only display the number of entry points found
+  -c, --cwd string                                                  Working directory for the command (default "$PWD")
+      --follow-monorepo-packages strings                            Enable resolution of imports from monorepo workspace packages. Pass without value to follow all, or pass package names
+      --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)
+      --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)
+  -v, --verbose                                                     Show warnings and verbose output
 ```
@@ -743,16 +777,16 @@ rev-dep files --entry-point src/index.ts
 #### Options
 ```
-      --condition-names strings    List of conditions for package.json imports resolution (e.g. node, imports, default)
-  -n, --count                      Only display the count of files in the dependency tree
-  -c, --cwd string                 Working directory for the command (default "$PWD")
-  -p, --entry-point string         Entry point file to analyze (required)
-      --follow-monorepo-packages   Enable resolution of imports from monorepo workspace packages
-  -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)
-      --tsconfig-json string       Path to tsconfig.json (default: ./tsconfig.json)
-  -v, --verbose                    Show warnings and verbose output
+      --condition-names strings                                     List of conditions for package.json imports resolution (e.g. node, imports, default)
+  -n, --count                                                       Only display the count of files in the dependency tree
+  -c, --cwd string                                                  Working directory for the command (default "$PWD")
+  -p, --entry-point string                                          Entry point file to analyze (required)
+      --follow-monorepo-packages strings                            Enable resolution of imports from monorepo workspace packages. Pass without value to follow all, or pass package names
+  -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)
+      --tsconfig-json string                                        Path to tsconfig.json (default: ./tsconfig.json)
+  -v, --verbose                                                     Show warnings and verbose output
 ```
@@ -778,16 +812,16 @@ rev-dep imported-by --file src/utils/helpers.ts
 #### Options
 ```
-      --condition-names strings    List of conditions for package.json imports resolution (e.g. node, imports, default)
-  -n, --count                      Only display the count of importing files
-  -c, --cwd string                 Working directory for the command (default "$PWD")
-  -f, --file string                Target file to find importers for (required)
-      --follow-monorepo-packages   Enable resolution of imports from monorepo workspace packages
-  -h, --help                       help for imported-by
-      --list-imports               List the import identifiers used by each file
-      --package-json string        Path to package.json (default: ./package.json)
-      --tsconfig-json string       Path to tsconfig.json (default: ./tsconfig.json)
-  -v, --verbose                    Show warnings and verbose output
+      --condition-names strings                                     List of conditions for package.json imports resolution (e.g. node, imports, default)
+  -n, --count                                                       Only display the count of importing files
+  -c, --cwd string                                                  Working directory for the command (default "$PWD")
+  -f, --file string                                                 Target file to find importers for (required)
+      --follow-monorepo-packages strings                            Enable resolution of imports from monorepo workspace packages. Pass without value to follow all, or pass package names
+  -h, --help                                                        help for imported-by
+      --list-imports                                                List the import identifiers used by each file
+      --package-json string                                         Path to package.json (default: ./package.json)
+      --tsconfig-json string                                        Path to tsconfig.json (default: ./tsconfig.json)
+  -v, --verbose                                                     Show warnings and verbose output
 ```
@@ -976,24 +1010,25 @@ rev-dep node-modules missing --entry-points=src/main.ts
 #### Options
 ```
-      --condition-names strings            List of conditions for package.json imports resolution (e.g. node, imports, default)
-  -n, --count                              Only display the count of modules
-  -c, --cwd string                         Working directory for the command (default "$PWD")
-  -p, --entry-points strings               Entry point file(s) to start analysis from (default: auto-detected)
-  -e, --exclude-modules strings            list of modules to exclude from the output
-  -b, --files-with-binaries strings        Additional files to search for binary usages. Use paths relative to cwd
-  -m, --files-with-node-modules strings    Additional files to search for module imports. Use paths relative to cwd
-      --follow-monorepo-packages           Enable resolution of imports from monorepo workspace packages
-      --group-by-file                      Organize output by project file path
-      --group-by-module                    Organize output by npm package name
-  -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)
-      --pkg-fields-with-binaries strings   Additional package.json fields to check for binary usages
-      --tsconfig-json string               Path to tsconfig.json (default: ./tsconfig.json)
-  -v, --verbose                            Show warnings and verbose output
-      --zero-exit-code                     Use this flag to always return zero exit code
+      --condition-names strings                                     List of conditions for package.json imports resolution (e.g. node, imports, default)
+  -n, --count                                                       Only display the count of modules
+  -c, --cwd string                                                  Working directory for the command (default "$PWD")
+  -p, --entry-points strings                                        Entry point file(s) to start analysis from (default: auto-detected)
+  -e, --exclude-modules strings                                     list of modules to exclude from the output
+  -b, --files-with-binaries strings                                 Additional files to search for binary usages. Use paths relative to cwd
+  -m, --files-with-node-modules strings                             Additional files to search for module imports. Use paths relative to cwd
+      --follow-monorepo-packages strings                            Enable resolution of imports from monorepo workspace packages. Pass without value to follow all, or pass package names
+      --group-by-file                                               Organize output by project file path
+      --group-by-module                                             Organize output by npm package name
+      --group-by-module-files-count                                 Organize output by npm package name and show count of files using it
+  -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)
+      --pkg-fields-with-binaries strings                            Additional package.json fields to check for binary usages
+      --tsconfig-json string                                        Path to tsconfig.json (default: ./tsconfig.json)
+  -v, --verbose                                                     Show warnings and verbose output
+      --zero-exit-code                                              Use this flag to always return zero exit code
 ```
@@ -1019,22 +1054,22 @@ rev-dep node-modules unused --exclude-modules=@types/*
 #### Options
 ```
-      --condition-names strings            List of conditions for package.json imports resolution (e.g. node, imports, default)
-  -n, --count                              Only display the count of modules
-  -c, --cwd string                         Working directory for the command (default "$PWD")
-  -p, --entry-points strings               Entry point file(s) to start analysis from (default: auto-detected)
-  -e, --exclude-modules strings            list of modules to exclude from the output
-  -b, --files-with-binaries strings        Additional files to search for binary usages. Use paths relative to cwd
-  -m, --files-with-node-modules strings    Additional files to search for module imports. Use paths relative to cwd
-      --follow-monorepo-packages           Enable resolution of imports from monorepo workspace packages
-  -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)
-      --pkg-fields-with-binaries strings   Additional package.json fields to check for binary usages
-      --tsconfig-json string               Path to tsconfig.json (default: ./tsconfig.json)
-  -v, --verbose                            Show warnings and verbose output
-      --zero-exit-code                     Use this flag to always return zero exit code
+      --condition-names strings                                     List of conditions for package.json imports resolution (e.g. node, imports, default)
+  -n, --count                                                       Only display the count of modules
+  -c, --cwd string                                                  Working directory for the command (default "$PWD")
+  -p, --entry-points strings                                        Entry point file(s) to start analysis from (default: auto-detected)
+  -e, --exclude-modules strings                                     list of modules to exclude from the output
+  -b, --files-with-binaries strings                                 Additional files to search for binary usages. Use paths relative to cwd
+  -m, --files-with-node-modules strings                             Additional files to search for module imports. Use paths relative to cwd
+      --follow-monorepo-packages strings                            Enable resolution of imports from monorepo workspace packages. Pass without value to follow all, or pass package names
+  -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)
+      --pkg-fields-with-binaries strings                            Additional package.json fields to check for binary usages
+      --tsconfig-json string                                        Path to tsconfig.json (default: ./tsconfig.json)
+  -v, --verbose                                                     Show warnings and verbose output
+      --zero-exit-code                                              Use this flag to always return zero exit code
 ```
@@ -1060,23 +1095,24 @@ rev-dep node-modules used -p src/index.ts --group-by-module
 #### Options
 ```
-      --condition-names strings            List of conditions for package.json imports resolution (e.g. node, imports, default)
-  -n, --count                              Only display the count of modules
-  -c, --cwd string                         Working directory for the command (default "$PWD")
-  -p, --entry-points strings               Entry point file(s) to start analysis from (default: auto-detected)
-  -e, --exclude-modules strings            list of modules to exclude from the output
-  -b, --files-with-binaries strings        Additional files to search for binary usages. Use paths relative to cwd
-  -m, --files-with-node-modules strings    Additional files to search for module imports. Use paths relative to cwd
-      --follow-monorepo-packages           Enable resolution of imports from monorepo workspace packages
-      --group-by-file                      Organize output by project file path
-      --group-by-module                    Organize output by npm package name
-  -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)
-      --pkg-fields-with-binaries strings   Additional package.json fields to check for binary usages
-      --tsconfig-json string               Path to tsconfig.json (default: ./tsconfig.json)
-  -v, --verbose                            Show warnings and verbose output
+      --condition-names strings                                     List of conditions for package.json imports resolution (e.g. node, imports, default)
+  -n, --count                                                       Only display the count of modules
+  -c, --cwd string                                                  Working directory for the command (default "$PWD")
+  -p, --entry-points strings                                        Entry point file(s) to start analysis from (default: auto-detected)
+  -e, --exclude-modules strings                                     list of modules to exclude from the output
+  -b, --files-with-binaries strings                                 Additional files to search for binary usages. Use paths relative to cwd
+  -m, --files-with-node-modules strings                             Additional files to search for module imports. Use paths relative to cwd
+      --follow-monorepo-packages strings                            Enable resolution of imports from monorepo workspace packages. Pass without value to follow all, or pass package names
+      --group-by-file                                               Organize output by project file path
+      --group-by-module                                             Organize output by npm package name
+      --group-by-module-files-count                                 Organize output by npm package name and show count of files using it
+  -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)
+      --pkg-fields-with-binaries strings                            Additional package.json fields to check for binary usages
+      --tsconfig-json string                                        Path to tsconfig.json (default: ./tsconfig.json)
+  -v, --verbose                                                     Show warnings and verbose output
 ```
@@ -1102,45 +1138,27 @@ rev-dep resolve -p src/index.ts -f src/utils/helpers.ts
 #### Options
 ```
-  -a, --all                        Show all possible resolution paths, not just the first one
-      --compact-summary            Display a compact summary of found paths
-      --condition-names strings    List of conditions for package.json imports resolution (e.g. node, imports, default)
-  -c, --cwd string                 Working directory for the command (default "$PWD")
-  -p, --entry-points strings       Entry point file(s) to start analysis from (default: auto-detected)
-  -f, --file string                Target file to check for dependencies
-      --follow-monorepo-packages   Enable resolution of imports from monorepo workspace packages
-      --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)
-      --tsconfig-json string       Path to tsconfig.json (default: ./tsconfig.json)
-  -v, --verbose                    Show warnings and verbose output
+  -a, --all                                                         Show all possible resolution paths, not just the first one
+      --compact-summary                                             Display a compact summary of found paths
+      --condition-names strings                                     List of conditions for package.json imports resolution (e.g. node, imports, default)
+  -c, --cwd string                                                  Working directory for the command (default "$PWD")
+  -p, --entry-points strings                                        Entry point file(s) to start analysis from (default: auto-detected)
+  -f, --file string                                                 Target file to check for dependencies
+      --follow-monorepo-packages strings                            Enable resolution of imports from monorepo workspace packages. Pass without value to follow all, or pass package names
+      --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)
+      --tsconfig-json string                                        Path to tsconfig.json (default: ./tsconfig.json)
+  -v, --verbose                                                     Show warnings and verbose output
 ```
 <!-- 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 script using skott `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
+## 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.
@@ -1202,4 +1220,4 @@ 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 ⭐!
+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/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "rev-dep",
-  "version": "2.6.1",
+  "version": "2.7.1",
   "description": "Trace imports, detect unused code, clean dependencies — all with a super-fast CLI",
   "bin": "bin.js",
   "files": [
@@ -17,9 +17,9 @@
     "node": ">=18"
   },
   "optionalDependencies": {
-    "@rev-dep/darwin-arm64": "2.6.1",
-    "@rev-dep/linux-x64": "2.6.1",
-    "@rev-dep/win32-x64": "2.6.1"
+    "@rev-dep/darwin-arm64": "2.7.1",
+    "@rev-dep/linux-x64": "2.7.1",
+    "@rev-dep/win32-x64": "2.7.1"
   },
   "keywords": [
     "dependency-analysis",