INCOMPLETE

	1. Add tests (for desired features added to docs) -> implement
	2. (apparent problem in eslint itself with our use of Program:exit):

test(`no-undefined-types`): issues gajus#507

Author: brettz9

.README/rules/no-undefined-types.md

@@ -43,12 +43,38 @@ reporting on use of that namepath elsewhere) and/or that a tag's `type` is
 
 #### Options
 
-An option object may have the following key:
+An option object may have the following keys, helping indicate types or
+file sources of types:
 
 - `definedTypes` - This array can be populated to indicate other types which
   are automatically considered as defined (in addition to globals, etc.).
   Defaults to an empty array.
 
+- `entryFiles` - Array of entry files objects indicating JavaScript or HTML
+  files whose `import` or `require` statements should be resolved recursively
+  and be analyzed for `@typedef`'s or globals to treat as "defined" for the
+  purposes of this rule. Each object should have a `file` array and with an
+  optional `node` property to indicate whether to use the Node Resolution
+  Algorithm (e.g., for Node.js) and/or `cjs` (if following `require`)
+  properties. Set one of the `file` items to `<main>`, `<exports>`,
+  `<exports.imports>`, or `<exports.require>` to use the file referenced in
+  the correpsonding property in `package.json`.
+
+- `jsdocConfig` - Object with:
+  - `file` string pointing to a path for a
+    [jsdoc config file](https://jsdoc.app/about-configuring-jsdoc.html)
+    which will be parsed for [input files](https://jsdoc.app/about-configuring-jsdoc.html#specifying-input-files),
+    including `include`, `exclude`, `includePattern`, and `excludePattern`
+    properties within the file as well as `opts.recurse`. See `entryFiles`
+    on how the (JavaScript) files will be treated (with
+    `sourceType: 'module'` in the jsdoc config file causing "cjs" to be
+    set to `false`).
+
+- `typeSources` - Array with `globals`, `exports`, and/or `locals` indicating
+    the source types that will be treated as valid types when found in the
+    current file or any entry files (`locals` will only apply to the
+    current file).
+
 |||
 |---|---|
 |Context|everywhere|

README.md

@@ -6848,12 +6848,38 @@ reporting on use of that namepath elsewhere) and/or that a tag's `type` is
 <a name="eslint-plugin-jsdoc-rules-no-undefined-types-options-16"></a>
 #### Options
 
-An option object may have the following key:
+An option object may have the following keys, helping indicate types or
+file sources of types:
 
 - `definedTypes` - This array can be populated to indicate other types which
   are automatically considered as defined (in addition to globals, etc.).
   Defaults to an empty array.
 
+- `entryFiles` - Array of entry files objects indicating JavaScript or HTML
+  files whose `import` or `require` statements should be resolved recursively
+  and be analyzed for `@typedef`'s or globals to treat as "defined" for the
+  purposes of this rule. Each object should have a `file` array and with an
+  optional `node` property to indicate whether to use the Node Resolution
+  Algorithm (e.g., for Node.js) and/or `cjs` (if following `require`)
+  properties. Set one of the `file` items to `<main>`, `<exports>`,
+  `<exports.imports>`, or `<exports.require>` to use the file referenced in
+  the correpsonding property in `package.json`.
+
+- `jsdocConfig` - Object with:
+  - `file` string pointing to a path for a
+    [jsdoc config file](https://jsdoc.app/about-configuring-jsdoc.html)
+    which will be parsed for [input files](https://jsdoc.app/about-configuring-jsdoc.html#specifying-input-files),
+    including `include`, `exclude`, `includePattern`, and `excludePattern`
+    properties within the file as well as `opts.recurse`. See `entryFiles`
+    on how the (JavaScript) files will be treated (with
+    `sourceType: 'module'` in the jsdoc config file causing "cjs" to be
+    set to `false`).
+
+- `typeSources` - Array with `globals`, `exports`, and/or `locals` indicating
+    the source types that will be treated as valid types when found in the
+    current file or any entry files (`locals` will only apply to the
+    current file).
+
 |||
 |---|---|
 |Context|everywhere|
@@ -7345,6 +7371,30 @@ function quux () {}
  * @type {SomeType}
  */
 // Settings: {"jsdoc":{"structuredTags":{"namepathDefiner":{"name":"namepath-defining"}}}}
+
+import {myTypesA} from '../internal/file.js'; // ERROR
+import {myTypesB} from '../internal/file.js'; // NO ERROR
+
+/**
+* @typedef newType
+* @property {myTypesA.someType} someProp - Some prop.
+*/
+
+/**
+* @param {newType} arg - Arg.
+*/
+function myFunctionA(arg) {
+    return arg;
+}
+
+/**
+* @param {myTypesB.someType} arg - Arg.
+*/
+function myFunctionB(arg) {
+    return arg;
+}
+
+export {myFunctionA, myFunctionB};
 ````
 
 

package.json

@@ -7,6 +7,7 @@
   "dependencies": {
     "comment-parser": "^0.7.6",
     "debug": "^4.1.1",
+    "es-file-traverse": "^0.1.2",
     "jsdoctypeparser": "^9.0.0",
     "lodash": "^4.17.20",
     "regextras": "^0.7.1",

test/rules/assertions/noUndefinedTypes.js

@@ -897,5 +897,38 @@ export default {
         },
       },
     },
+    {
+      code: `
+      import {myTypesA} from '../internal/file.js'; // ERROR
+      import {myTypesB} from '../internal/file.js'; // NO ERROR
+
+      /**
+      * @typedef newType
+      * @property {myTypesA.someType} someProp - Some prop.
+      */
+
+      /**
+      * @param {newType} arg - Arg.
+      */
+      function myFunctionA(arg) {
+          return arg;
+      }
+
+      /**
+      * @param {myTypesB.someType} arg - Arg.
+      */
+      function myFunctionB(arg) {
+          return arg;
+      }
+
+      export {myFunctionA, myFunctionB};
+      `,
+      parserOptions: {
+        sourceType: 'module',
+      },
+      rules: {
+        'no-unused-vars': ['error'],
+      },
+    },
   ],
 };