used-deps-analyzer

Analyse js code to force match between installed & used deps

Installation

1$ npm install used-deps-analyzer

Features

• Analyse a directory content to find unused installed deps
• Analyse a directory content to find used uninstalled deps

Doc

Content

check the TypeScript definition file

Examples

check the TypeScript compilation tests

Options

• noDev | --no-dev : do not use dev deps for comparaison (used files, don't use it to analyze test or build scripts)
• onlyDev | --only-dev : use only dev deps for comparaison (test or build scripts, don't use it to analyze used files)
• overkill | --overkill : list of deps which should not be used but can be still present for unknown reasons (do not fail, trigger only warnings)
• misscalled | --misscalled Array : list of deps which are not called by this name in the code
• shadows | --shadows Array : list of deps which are used in the code but not required (to force a sub-dep version for example)

1interface iSubModule {
2	"module": string;
3	"call": string;
4}

Run

1cd ./myProject/ && npx used-deps-analyzer -- "./package.json" "./dir" --no-dev

1const usedDepsAnalyzer = require("used-deps-analyzer");
2
3usedDepsAnalyzer("./package.json", "./src", {
4	"noDev": true,
5	"overkill": [
6		"node-promfs"
7	],
8	"misscalled": [
9		{
10			"module": "colors",
11			"call": "colors/safe"
12		}
13	],
14	"shadows": [
15		"newer-version",
16		"not-called-front-lib"
17	]
18}).then((analyze) => {
19
20	if (analyze.warnings) {
21
22		analyze.warnings.forEach((a) => {
23			console.warn(a);
24		});
25
26	}
27
28	if (analyze.result) {
29		console.log("all ok");
30	}
31	else {
32
33		analyze.errors.forEach((a) => {
34			console.error(a);
35		});
36
37	}
38
39}).catch((err) => {
40	console.log(err);
41});

Tests

1$ npm run-script tests

License

ISC