package
Node dependency usage checker using V8 Coverage
npm install depsGitHub-flavored package documentation.
Across all versions.
Download trend unavailable.
Runtime metadata.
Tagged topics.
Accurately detect which Node dependencies are in-use with V8 Coverage 🔥
$ npx deps [...command]eg. npx deps npm run build
Install globally if you don't want to use it via npx.
npm i -g depsPrefix your Node command with deps and it will analyze and output the dependencies it used
$ deps ...eg. deps npm run build
Prerequisite: install deps globally
$ . deps-startnpm run devnpm run buildnpm run lint$ deps analyzedeps analyze -o output.jsondeps -f output.json$ . deps-stopdeps detects which modules are loaded by using V8's code coverage feature, so it's very accurate. However, it doesn't detect file-system reads, as they are simply read as text rather than actually being parsed and executed. That means it can't detect what files are statically analyzed by bundlers (eg. Webpack, Rollup, etc.). I am considering supporting FS reads in the future.
depcheck?depcheck statically analyzes your project to see which dependencies are imported, avoiding the need to execute code. In contrast, deps executes code to analyze which dependencies were loaded during run-time. They work in completely different ways, but a major drawback for me is that depcheck requires a "special" for supporting whether a module was loaded via dev-tools.
MIT
Estimated unpacked size across 55 packages.
2.4 MB
Includes dependencies.
1.1.1