Throw for invalid issue types when using include/exclude filter (closes #366)

Author: webpro

packages/docs/src/content/docs/reference/issue-types.md

@@ -25,7 +25,9 @@ Knip reports the following types of issues:
 - NSs = namespaces
 - When an issue type has zero issues, it is not shown.
 
-Note that `devDependencies` is covered with a single key for all `dependencies`.
-In [strict production mode][1], `devDependencies` are not included.
+The `devDependencies` are covered in a single key for all `dependencies`. In
+[strict production mode][1], `devDependencies` are not included.
+
+The `types` issue type includes `enum`, `interface` and `type` exports.
 
 [1]: ../features/production-mode.md#strict-mode

packages/knip/src/util/cli-arguments.ts

@@ -14,7 +14,7 @@ Options:
   --no-gitignore           Don't use .gitignore
   --include                Report only provided issue type(s), can be comma-separated or repeated (1)
   --exclude                Exclude provided issue type(s) from report, can be comma-separated or repeated (1)
-  --dependencies           Shortcut for --include dependencies,unlisted,unresolved
+  --dependencies           Shortcut for --include dependencies,unlisted,binaries,unresolved
   --exports                Shortcut for --include exports,nsExports,classMembers,types,nsTypes,enumMembers,duplicates
   --include-entry-exports  Include entry files when reporting unused exports
   --isolate-workspaces     Isolated workspaces in monorepo

packages/knip/src/util/get-included-issue-types.ts

@@ -1,4 +1,5 @@
 import { ISSUE_TYPES } from '../constants.js';
+import { ConfigurationError } from './errors.js';
 import type { Report } from '../types/issues.js';
 
 type CLIArguments = {
@@ -20,6 +21,11 @@ export const getIncludedIssueTypes = (
   cliArgs: CLIArguments,
   { include = [], exclude = [], isProduction = false }: Options = {}
 ) => {
+  [...cliArgs.include, ...cliArgs.exclude, ...include, ...exclude].forEach(type => {
+    // @ts-expect-error The point is that we're checking for invalid issue types
+    if (!ISSUE_TYPES.includes(type)) throw new ConfigurationError(`Invalid issue type: ${type}`);
+  });
+
   if (cliArgs.dependencies) {
     cliArgs.include = [
       ...cliArgs.include,