Available Rules
The --fix option on the command line automatically fixes problems reported by rules which have a wrench 🔧 below.
The rules with the following star ⭐ are included in the configs.recommended config.
Possible Errors
| Rule ID | Description | |
|---|---|---|
| node-dependencies/compat-engines | enforce the versions of the engines of the dependencies to be compatible. | ⭐ |
| node-dependencies/no-dupe-deps | disallow duplicate dependencies. | ⭐ |
| node-dependencies/valid-semver | enforce versions that is valid as a semantic version. | ⭐ |
Best Practices
| Rule ID | Description | |
|---|---|---|
| node-dependencies/absolute-version | require or disallow absolute version of dependency. | |
| node-dependencies/no-deprecated | disallow having dependencies on deprecate packages. | |
| node-dependencies/no-restricted-deps | Disallows dependence on the specified package. | |
| node-dependencies/require-provenance-deps | Require provenance information for dependencies |
Stylistic Issues
| Rule ID | Description | |
|---|---|---|
| node-dependencies/prefer-caret-range-version | require caret(^) version instead of range version. | 🔧 |
| node-dependencies/prefer-tilde-range-version | require tilde(~) version instead of range version. | 🔧 |
Deprecated
- ⚠️ We're going to remove deprecated rules in the next major release. Please migrate to successor/new rules.
- 😇 We don't fix bugs which are in deprecated rules since we don't have enough resources.
| Rule ID | Replaced by |
|---|---|
| node-dependencies/valid-engines | node-dependencies/compat-engines |