hitstrio.blogg.se - Npm devdependencies vs dependencies

This project exists thanks to all the people who contribute.īecome a financial contributor and help us sustain our community. We use the GitHub release page to manage changelog.

How are you using those dependencies, what do the files look like?.

Which dependencies are considered as false alert?.

The output from depcheck -json command.

If you find that depcheck is reporting a false alert, please open an issue with the following information to let us know: There may be some cases in which a dependency is being used but is reported as unused, or a dependency is not used but is reported as missing. However, the predefined rules may not be enough or may even be wrong. The value is the error details.ĭepcheck just walks through all files and tries to find the dependencies according to some predefined rules.

The invalidDirs property contains the directories having permission error.

However, only one error is stored in the lookup.

The invalidFiles property contains the files having syntax error or permission error.

It means the dependency may be used by many files.

The value of missing and using lookup is an array.

The using property is a lookup indicating each dependency is used by which files.

The dependencies, devDependencies and missing properties have the same meanings in the previous example.

Import depcheck from 'depcheck' const options =

depcheckrc file in your project's package.json folder, and set the CLI keys in YAML, JSON, and Javascript formats.įor example, the CLI arguments -ignores="eslint,babel-*" -skip-missing=true would turn into: Usage with a configuration fileĭepcheck can be used with an rc configuration file.

config=: An external configuration file (see below).

Check the pluggable design document for more information. They provide an easy way to customize the file parser and dependency detection. parsers, -detectors and -specials: These arguments are for advanced usage. Example, -ignore-patterns=build/Release,dist,coverage,*.log. ignore-patterns: Comma separated patterns describing files to ignore. ignore-path: Path to a file with patterns describing files to ignore. A comma separated array containing directory names to ignore. ignore-dirs: DEPRECATED, use ignore-patterns instead. ignores: A comma separated array containing package names to ignore. oneline: Output results as space separated string. When not specified, depcheck outputs in human friendly format. skip-missing=: A flag to indicate if depcheck skips calculation of missing dependencies. ignore-bin-package=: A flag to indicate if depcheck ignores the packages containing bin entry. If unspecified, defaults to current directory. The directory argument is the root directory of your project (where the package.json file is). If this happens, please open an issue for us. tslint - TSLint configuration presets, parsers and plugins.prettier - Prettier configuration module.mocha - Mocha explicit required dependencies.lint-staged - Lint-staged configuration parser.karma - Karma configuration frameworks, browsers, preprocessors and reporters.jest - Jest properties in Jest Configuration.istanbul - Istanbul nyc configuration extensions.gulp-load-plugins - Gulp-load-plugins lazy loaded plugins.feross-standard - Feross standard format parser.eslint - ESLint configuration presets, parsers and plugins.commitizen - Commitizen configuration adaptor.bin - Dependencies used in npm commands, Travis scripts or other CI scripts.

The following scenarios are supported by specials: The special component is used to recognize the dependencies that are not generally used in the above syntax files.