@wo658/redpact 0.4.1 → 0.5.0

package/node_modules/@rushstack/node-core-library/lib/IPackageJson.d.ts

@@ -0,0 +1,295 @@
+/**
+ * This interface is part of the {@link IPackageJson} file format.  It is used for the
+ * "dependencies", "optionalDependencies", and "devDependencies" fields.
+ * @public
+ */
+export interface IPackageJsonDependencyTable {
+    /**
+     * The key is the name of a dependency.  The value is a Semantic Versioning (SemVer)
+     * range specifier.
+     */
+    [dependencyName: string]: string;
+}
+/**
+ * This interface is part of the {@link IPackageJson} file format.  It is used for the
+ * "scripts" field.
+ * @public
+ */
+export interface IPackageJsonScriptTable {
+    /**
+     * The key is the name of the script hook.  The value is the script body which may
+     * be a file path or shell script command.
+     */
+    [scriptName: string]: string;
+}
+/**
+ * This interface is part of the {@link IPackageJson} file format.  It is used for the
+ * "repository" field.
+ * @public
+ */
+export interface IPackageJsonRepository {
+    /**
+     * The source control type for the repository that hosts the project. This is typically "git".
+     */
+    type: string;
+    /**
+     * The URL of the repository that hosts the project.
+     */
+    url: string;
+    /**
+     * If the project does not exist at the root of the repository, its path is specified here.
+     */
+    directory?: string;
+}
+/**
+ * This interface is part of the {@link IPackageJson} file format. It is used for the
+ * "peerDependenciesMeta" field.
+ * @public
+ */
+export interface IPeerDependenciesMetaTable {
+    [dependencyName: string]: {
+        optional?: boolean;
+    };
+}
+/**
+ * This interface is part of the {@link IPackageJson} file format. It is used for the
+ * "dependenciesMeta" field.
+ * @public
+ */
+export interface IDependenciesMetaTable {
+    [dependencyName: string]: {
+        injected?: boolean;
+    };
+}
+/**
+ * This interface is part of the {@link IPackageJson} file format. It is used for the values
+ * of the "exports" field.
+ *
+ * See {@link https://nodejs.org/api/packages.html#conditional-exports | Node.js documentation on Conditional Exports} and
+ * {@link https://nodejs.org/api/packages.html#community-conditions-definitions | Node.js documentation on Community Conditional Exports}.
+ *
+ * @public
+ */
+export interface IPackageJsonExports {
+    /**
+     * This export is like {@link IPackageJsonExports.node} in that it matches for any NodeJS environment.
+     * This export is specifically for native C++ addons.
+     */
+    'node-addons'?: string | IPackageJsonExports;
+    /**
+     * This export matches for any NodeJS environment.
+     */
+    node?: string | IPackageJsonExports;
+    /**
+     * This export matches when loaded via ESM syntax (i.e. - `import '...'` or `import('...')`).
+     * This is always mutually exclusive with {@link IPackageJsonExports.require}.
+     */
+    import?: string | IPackageJsonExports;
+    /**
+     * This export matches when loaded via `require()`.
+     * This is always mutually exclusive with {@link IPackageJsonExports.import}.
+     */
+    require?: string | IPackageJsonExports;
+    /**
+     * This export matches as a fallback when no other conditions match. Because exports are evaluated in
+     * the order that they are specified in the `package.json` file, this condition should always come last
+     * as no later exports will match if this one does.
+     */
+    default?: string | IPackageJsonExports;
+    /**
+     * This export matches when loaded by the typing system (i.e. - the TypeScript compiler).
+     */
+    types?: string | IPackageJsonExports;
+    /**
+     * Any web browser environment.
+     */
+    browser?: string | IPackageJsonExports;
+    /**
+     * This export matches in development-only environments.
+     * This is always mutually exclusive with {@link IPackageJsonExports.production}.
+     */
+    development?: string | IPackageJsonExports;
+    /**
+     * This export matches in production-only environments.
+     * This is always mutually exclusive with {@link IPackageJsonExports.development}.
+     */
+    production?: string | IPackageJsonExports;
+}
+/**
+ * An interface for accessing common fields from a package.json file whose version field may be missing.
+ *
+ * @remarks
+ * This interface is the same as {@link IPackageJson}, except that the `version` field is optional.
+ * According to the {@link https://docs.npmjs.com/files/package.json | NPM documentation}
+ * and {@link http://wiki.commonjs.org/wiki/Packages/1.0 | CommonJS Packages specification}, the `version` field
+ * is normally a required field for package.json files.
+ *
+ * However, NodeJS relaxes this requirement for its `require()` API.  The
+ * {@link https://nodejs.org/dist/latest-v10.x/docs/api/modules.html#modules_folders_as_modules
+ * | "Folders as Modules" section} from the NodeJS documentation gives an example of a package.json file
+ * that has only the `name` and `main` fields.  NodeJS does not consider the `version` field during resolution,
+ * so it can be omitted.  Some libraries do this.
+ *
+ * Use the `INodePackageJson` interface when loading such files.  Use `IPackageJson` for package.json files
+ * that are installed from an NPM registry, or are otherwise known to have a `version` field.
+ *
+ * @public
+ */
+export interface INodePackageJson {
+    /**
+     * The name of the package.
+     */
+    name: string;
+    /**
+     * A version number conforming to the Semantic Versioning (SemVer) standard.
+     */
+    version?: string;
+    /**
+     * Indicates whether this package is allowed to be published or not.
+     */
+    private?: boolean;
+    /**
+     * A brief description of the package.
+     */
+    description?: string;
+    /**
+     * The URL of the project's repository.
+     */
+    repository?: string | IPackageJsonRepository;
+    /**
+     * The URL to the project's web page.
+     */
+    homepage?: string;
+    /**
+     * The name of the license.
+     */
+    license?: string;
+    /**
+     * The path to the module file that will act as the main entry point.
+     */
+    main?: string;
+    /**
+     * The path to the TypeScript *.d.ts file describing the module file
+     * that will act as the main entry point.
+     */
+    types?: string;
+    /**
+     * Alias for `types`
+     */
+    typings?: string;
+    /**
+     * The path to the TSDoc metadata file.
+     * This is still being standardized: https://github.com/microsoft/tsdoc/issues/7#issuecomment-442271815
+     * @beta
+     */
+    tsdocMetadata?: string;
+    /**
+     * The main entry point for the package.
+     */
+    bin?: string | Record<string, string>;
+    /**
+     * An array of dependencies that must always be installed for this package.
+     */
+    dependencies?: IPackageJsonDependencyTable;
+    /**
+     * An array of optional dependencies that may be installed for this package.
+     */
+    optionalDependencies?: IPackageJsonDependencyTable;
+    /**
+     * An array of dependencies that must only be installed for developers who will
+     * build this package.
+     */
+    devDependencies?: IPackageJsonDependencyTable;
+    /**
+     * An array of dependencies that must be installed by a consumer of this package,
+     * but which will not be automatically installed by this package.
+     */
+    peerDependencies?: IPackageJsonDependencyTable;
+    /**
+     * An array of metadata for dependencies declared inside dependencies, optionalDependencies, and devDependencies.
+     * https://pnpm.io/package_json#dependenciesmeta
+     */
+    dependenciesMeta?: IDependenciesMetaTable;
+    /**
+     * An array of metadata about peer dependencies.
+     */
+    peerDependenciesMeta?: IPeerDependenciesMetaTable;
+    /**
+     * A table of script hooks that a package manager or build tool may invoke.
+     */
+    scripts?: IPackageJsonScriptTable;
+    /**
+     * A table of package version resolutions. This feature is only implemented by the Yarn package manager.
+     *
+     * @remarks
+     * See the {@link https://github.com/yarnpkg/rfcs/blob/master/implemented/0000-selective-versions-resolutions.md
+     * | 0000-selective-versions-resolutions.md RFC} for details.
+     */
+    resolutions?: Record<string, string>;
+    /**
+     * A table of TypeScript *.d.ts file paths that are compatible with specific TypeScript version
+     * selectors. This data take a form similar to that of the {@link INodePackageJson.exports} field,
+     * with fallbacks listed in order in the value array for example:
+     *
+     * ```JSON
+     * "typesVersions": {
+     *   ">=3.1": {
+     *     "*": ["./types-3.1/*", "./types-3.1-fallback/*"]
+     *   },
+     *   ">=3.0": {
+     *     "*": ["./types-legacy/*"]
+     *   }
+     * }
+     * ```
+     *
+     * or
+     *
+     * ```JSON
+     * "typesVersions": {
+     *   ">=3.1": {
+     *     "app/*": ["./app/types-3.1/*"],
+     *     "lib/*": ["./lib/types-3.1/*"]
+     *   },
+     *   ">=3.0": {
+     *     "app/*": ["./app/types-legacy/*"],
+     *     "lib/*": ["./lib/types-legacy/*"]
+     *   }
+     * }
+     * ```
+     *
+     * See the
+     * {@link https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html#version-selection-with-typesversions
+     * | TypeScript documentation} for details.
+     */
+    typesVersions?: Record<string, Record<string, [string, ...string[]]>>;
+    /**
+     * The "exports" field is used to specify the entry points for a package.
+     * See {@link https://nodejs.org/api/packages.html#exports | Node.js documentation}
+     */
+    exports?: string | string[] | Record<string, null | string | IPackageJsonExports>;
+    /**
+     * The "files" field is an array of file globs that should be included in the package during publishing.
+     *
+     * See the {@link https://docs.npmjs.com/cli/v6/configuring-npm/package-json#files | NPM documentation}.
+     */
+    files?: string[];
+}
+/**
+ * An interface for accessing common fields from a package.json file.
+ *
+ * @remarks
+ * This interface describes a package.json file format whose `name` and `version` field are required.
+ * In some situations, the `version` field is optional; in that case, use the {@link INodePackageJson}
+ * interface instead.
+ *
+ * More fields may be added to this interface in the future.  For documentation about the package.json file format,
+ * see the {@link http://wiki.commonjs.org/wiki/Packages/1.0 | CommonJS Packages specification}
+ * and the {@link https://docs.npmjs.com/files/package.json | NPM manual page}.
+ *
+ * @public
+ */
+export interface IPackageJson extends INodePackageJson {
+    /** {@inheritDoc INodePackageJson.version} */
+    version: string;
+}
+//# sourceMappingURL=IPackageJson.d.ts.map

package/node_modules/@rushstack/node-core-library/lib/IPackageJson.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"IPackageJson.d.ts","sourceRoot":"","sources":["../src/IPackageJson.ts"],"names":[],"mappings":"AAGA;;;;GAIG;AACH,MAAM,WAAW,2BAA2B;IAC1C;;;OAGG;IACH,CAAC,cAAc,EAAE,MAAM,GAAG,MAAM,CAAC;CAClC;AAED;;;;GAIG;AACH,MAAM,WAAW,uBAAuB;IACtC;;;OAGG;IACH,CAAC,UAAU,EAAE,MAAM,GAAG,MAAM,CAAC;CAC9B;AAED;;;;GAIG;AACH,MAAM,WAAW,sBAAsB;IACrC;;OAEG;IACH,IAAI,EAAE,MAAM,CAAC;IAEb;;OAEG;IACH,GAAG,EAAE,MAAM,CAAC;IAEZ;;OAEG;IACH,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAED;;;;GAIG;AACH,MAAM,WAAW,0BAA0B;IACzC,CAAC,cAAc,EAAE,MAAM,GAAG;QACxB,QAAQ,CAAC,EAAE,OAAO,CAAC;KACpB,CAAC;CACH;AAED;;;;GAIG;AACH,MAAM,WAAW,sBAAsB;IACrC,CAAC,cAAc,EAAE,MAAM,GAAG;QACxB,QAAQ,CAAC,EAAE,OAAO,CAAC;KACpB,CAAC;CACH;AAED;;;;;;;;GAQG;AACH,MAAM,WAAW,mBAAmB;IAClC;;;OAGG;IACH,aAAa,CAAC,EAAE,MAAM,GAAG,mBAAmB,CAAC;IAE7C;;OAEG;IACH,IAAI,CAAC,EAAE,MAAM,GAAG,mBAAmB,CAAC;IAEpC;;;OAGG;IACH,MAAM,CAAC,EAAE,MAAM,GAAG,mBAAmB,CAAC;IAEtC;;;OAGG;IACH,OAAO,CAAC,EAAE,MAAM,GAAG,mBAAmB,CAAC;IAEvC;;;;OAIG;IACH,OAAO,CAAC,EAAE,MAAM,GAAG,mBAAmB,CAAC;IAEvC;;OAEG;IACH,KAAK,CAAC,EAAE,MAAM,GAAG,mBAAmB,CAAC;IAErC;;OAEG;IACH,OAAO,CAAC,EAAE,MAAM,GAAG,mBAAmB,CAAC;IAEvC;;;OAGG;IACH,WAAW,CAAC,EAAE,MAAM,GAAG,mBAAmB,CAAC;IAE3C;;;OAGG;IACH,UAAU,CAAC,EAAE,MAAM,GAAG,mBAAmB,CAAC;CAC3C;AAED;;;;;;;;;;;;;;;;;;;GAmBG;AACH,MAAM,WAAW,gBAAgB;IAC/B;;OAEG;IACH,IAAI,EAAE,MAAM,CAAC;IAEb;;OAEG;IACH,OAAO,CAAC,EAAE,MAAM,CAAC;IAEjB;;OAEG;IACH,OAAO,CAAC,EAAE,OAAO,CAAC;IAElB;;OAEG;IACH,WAAW,CAAC,EAAE,MAAM,CAAC;IAErB;;OAEG;IACH,UAAU,CAAC,EAAE,MAAM,GAAG,sBAAsB,CAAC;IAE7C;;OAEG;IACH,QAAQ,CAAC,EAAE,MAAM,CAAC;IAElB;;OAEG;IACH,OAAO,CAAC,EAAE,MAAM,CAAC;IAEjB;;OAEG;IACH,IAAI,CAAC,EAAE,MAAM,CAAC;IAEd;;;OAGG;IACH,KAAK,CAAC,EAAE,MAAM,CAAC;IAEf;;OAEG;IACH,OAAO,CAAC,EAAE,MAAM,CAAC;IAEjB;;;;OAIG;IACH,aAAa,CAAC,EAAE,MAAM,CAAC;IAEvB;;OAEG;IACH,GAAG,CAAC,EAAE,MAAM,GAAG,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IAEtC;;OAEG;IACH,YAAY,CAAC,EAAE,2BAA2B,CAAC;IAE3C;;OAEG;IACH,oBAAoB,CAAC,EAAE,2BAA2B,CAAC;IAEnD;;;OAGG;IACH,eAAe,CAAC,EAAE,2BAA2B,CAAC;IAE9C;;;OAGG;IACH,gBAAgB,CAAC,EAAE,2BAA2B,CAAC;IAE/C;;;OAGG;IACH,gBAAgB,CAAC,EAAE,sBAAsB,CAAC;IAE1C;;OAEG;IACH,oBAAoB,CAAC,EAAE,0BAA0B,CAAC;IAElD;;OAEG;IACH,OAAO,CAAC,EAAE,uBAAuB,CAAC;IAElC;;;;;;OAMG;IACH,WAAW,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IAErC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OAkCG;IACH,aAAa,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,CAAC,MAAM,EAAE,GAAG,MAAM,EAAE,CAAC,CAAC,CAAC,CAAC;IAEtE;;;OAGG;IAEH,OAAO,CAAC,EAAE,MAAM,GAAG,MAAM,EAAE,GAAG,MAAM,CAAC,MAAM,EAAE,IAAI,GAAG,MAAM,GAAG,mBAAmB,CAAC,CAAC;IAElF;;;;OAIG;IACH,KAAK,CAAC,EAAE,MAAM,EAAE,CAAC;CAClB;AAED;;;;;;;;;;;;;GAaG;AACH,MAAM,WAAW,YAAa,SAAQ,gBAAgB;IAEpD,6CAA6C;IAC7C,OAAO,EAAE,MAAM,CAAC;CACjB"}

package/node_modules/@rushstack/node-core-library/lib/IPackageJson.js

@@ -0,0 +1,5 @@
+"use strict";
+// Copyright (c) Microsoft Corporation. All rights reserved. Licensed under the MIT license.
+// See LICENSE in the project root for license information.
+Object.defineProperty(exports, "__esModule", { value: true });
+//# sourceMappingURL=IPackageJson.js.map

package/node_modules/@rushstack/node-core-library/lib/IPackageJson.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"IPackageJson.js","sourceRoot":"","sources":["../src/IPackageJson.ts"],"names":[],"mappings":";AAAA,4FAA4F;AAC5F,2DAA2D","sourcesContent":["// Copyright (c) Microsoft Corporation. All rights reserved. Licensed under the MIT license.\n// See LICENSE in the project root for license information.\n\n/**\n * This interface is part of the {@link IPackageJson} file format.  It is used for the\n * \"dependencies\", \"optionalDependencies\", and \"devDependencies\" fields.\n * @public\n */\nexport interface IPackageJsonDependencyTable {\n  /**\n   * The key is the name of a dependency.  The value is a Semantic Versioning (SemVer)\n   * range specifier.\n   */\n  [dependencyName: string]: string;\n}\n\n/**\n * This interface is part of the {@link IPackageJson} file format.  It is used for the\n * \"scripts\" field.\n * @public\n */\nexport interface IPackageJsonScriptTable {\n  /**\n   * The key is the name of the script hook.  The value is the script body which may\n   * be a file path or shell script command.\n   */\n  [scriptName: string]: string;\n}\n\n/**\n * This interface is part of the {@link IPackageJson} file format.  It is used for the\n * \"repository\" field.\n * @public\n */\nexport interface IPackageJsonRepository {\n  /**\n   * The source control type for the repository that hosts the project. This is typically \"git\".\n   */\n  type: string;\n\n  /**\n   * The URL of the repository that hosts the project.\n   */\n  url: string;\n\n  /**\n   * If the project does not exist at the root of the repository, its path is specified here.\n   */\n  directory?: string;\n}\n\n/**\n * This interface is part of the {@link IPackageJson} file format. It is used for the\n * \"peerDependenciesMeta\" field.\n * @public\n */\nexport interface IPeerDependenciesMetaTable {\n  [dependencyName: string]: {\n    optional?: boolean;\n  };\n}\n\n/**\n * This interface is part of the {@link IPackageJson} file format. It is used for the\n * \"dependenciesMeta\" field.\n * @public\n */\nexport interface IDependenciesMetaTable {\n  [dependencyName: string]: {\n    injected?: boolean;\n  };\n}\n\n/**\n * This interface is part of the {@link IPackageJson} file format. It is used for the values\n * of the \"exports\" field.\n *\n * See {@link https://nodejs.org/api/packages.html#conditional-exports | Node.js documentation on Conditional Exports} and\n * {@link https://nodejs.org/api/packages.html#community-conditions-definitions | Node.js documentation on Community Conditional Exports}.\n *\n * @public\n */\nexport interface IPackageJsonExports {\n  /**\n   * This export is like {@link IPackageJsonExports.node} in that it matches for any NodeJS environment.\n   * This export is specifically for native C++ addons.\n   */\n  'node-addons'?: string | IPackageJsonExports;\n\n  /**\n   * This export matches for any NodeJS environment.\n   */\n  node?: string | IPackageJsonExports;\n\n  /**\n   * This export matches when loaded via ESM syntax (i.e. - `import '...'` or `import('...')`).\n   * This is always mutually exclusive with {@link IPackageJsonExports.require}.\n   */\n  import?: string | IPackageJsonExports;\n\n  /**\n   * This export matches when loaded via `require()`.\n   * This is always mutually exclusive with {@link IPackageJsonExports.import}.\n   */\n  require?: string | IPackageJsonExports;\n\n  /**\n   * This export matches as a fallback when no other conditions match. Because exports are evaluated in\n   * the order that they are specified in the `package.json` file, this condition should always come last\n   * as no later exports will match if this one does.\n   */\n  default?: string | IPackageJsonExports;\n\n  /**\n   * This export matches when loaded by the typing system (i.e. - the TypeScript compiler).\n   */\n  types?: string | IPackageJsonExports;\n\n  /**\n   * Any web browser environment.\n   */\n  browser?: string | IPackageJsonExports;\n\n  /**\n   * This export matches in development-only environments.\n   * This is always mutually exclusive with {@link IPackageJsonExports.production}.\n   */\n  development?: string | IPackageJsonExports;\n\n  /**\n   * This export matches in production-only environments.\n   * This is always mutually exclusive with {@link IPackageJsonExports.development}.\n   */\n  production?: string | IPackageJsonExports;\n}\n\n/**\n * An interface for accessing common fields from a package.json file whose version field may be missing.\n *\n * @remarks\n * This interface is the same as {@link IPackageJson}, except that the `version` field is optional.\n * According to the {@link https://docs.npmjs.com/files/package.json | NPM documentation}\n * and {@link http://wiki.commonjs.org/wiki/Packages/1.0 | CommonJS Packages specification}, the `version` field\n * is normally a required field for package.json files.\n *\n * However, NodeJS relaxes this requirement for its `require()` API.  The\n * {@link https://nodejs.org/dist/latest-v10.x/docs/api/modules.html#modules_folders_as_modules\n * | \"Folders as Modules\" section} from the NodeJS documentation gives an example of a package.json file\n * that has only the `name` and `main` fields.  NodeJS does not consider the `version` field during resolution,\n * so it can be omitted.  Some libraries do this.\n *\n * Use the `INodePackageJson` interface when loading such files.  Use `IPackageJson` for package.json files\n * that are installed from an NPM registry, or are otherwise known to have a `version` field.\n *\n * @public\n */\nexport interface INodePackageJson {\n  /**\n   * The name of the package.\n   */\n  name: string;\n\n  /**\n   * A version number conforming to the Semantic Versioning (SemVer) standard.\n   */\n  version?: string;\n\n  /**\n   * Indicates whether this package is allowed to be published or not.\n   */\n  private?: boolean;\n\n  /**\n   * A brief description of the package.\n   */\n  description?: string;\n\n  /**\n   * The URL of the project's repository.\n   */\n  repository?: string | IPackageJsonRepository;\n\n  /**\n   * The URL to the project's web page.\n   */\n  homepage?: string;\n\n  /**\n   * The name of the license.\n   */\n  license?: string;\n\n  /**\n   * The path to the module file that will act as the main entry point.\n   */\n  main?: string;\n\n  /**\n   * The path to the TypeScript *.d.ts file describing the module file\n   * that will act as the main entry point.\n   */\n  types?: string;\n\n  /**\n   * Alias for `types`\n   */\n  typings?: string;\n\n  /**\n   * The path to the TSDoc metadata file.\n   * This is still being standardized: https://github.com/microsoft/tsdoc/issues/7#issuecomment-442271815\n   * @beta\n   */\n  tsdocMetadata?: string;\n\n  /**\n   * The main entry point for the package.\n   */\n  bin?: string | Record<string, string>;\n\n  /**\n   * An array of dependencies that must always be installed for this package.\n   */\n  dependencies?: IPackageJsonDependencyTable;\n\n  /**\n   * An array of optional dependencies that may be installed for this package.\n   */\n  optionalDependencies?: IPackageJsonDependencyTable;\n\n  /**\n   * An array of dependencies that must only be installed for developers who will\n   * build this package.\n   */\n  devDependencies?: IPackageJsonDependencyTable;\n\n  /**\n   * An array of dependencies that must be installed by a consumer of this package,\n   * but which will not be automatically installed by this package.\n   */\n  peerDependencies?: IPackageJsonDependencyTable;\n\n  /**\n   * An array of metadata for dependencies declared inside dependencies, optionalDependencies, and devDependencies.\n   * https://pnpm.io/package_json#dependenciesmeta\n   */\n  dependenciesMeta?: IDependenciesMetaTable;\n\n  /**\n   * An array of metadata about peer dependencies.\n   */\n  peerDependenciesMeta?: IPeerDependenciesMetaTable;\n\n  /**\n   * A table of script hooks that a package manager or build tool may invoke.\n   */\n  scripts?: IPackageJsonScriptTable;\n\n  /**\n   * A table of package version resolutions. This feature is only implemented by the Yarn package manager.\n   *\n   * @remarks\n   * See the {@link https://github.com/yarnpkg/rfcs/blob/master/implemented/0000-selective-versions-resolutions.md\n   * | 0000-selective-versions-resolutions.md RFC} for details.\n   */\n  resolutions?: Record<string, string>;\n\n  /**\n   * A table of TypeScript *.d.ts file paths that are compatible with specific TypeScript version\n   * selectors. This data take a form similar to that of the {@link INodePackageJson.exports} field,\n   * with fallbacks listed in order in the value array for example:\n   *\n   * ```JSON\n   * \"typesVersions\": {\n   *   \">=3.1\": {\n   *     \"*\": [\"./types-3.1/*\", \"./types-3.1-fallback/*\"]\n   *   },\n   *   \">=3.0\": {\n   *     \"*\": [\"./types-legacy/*\"]\n   *   }\n   * }\n   * ```\n   *\n   * or\n   *\n   * ```JSON\n   * \"typesVersions\": {\n   *   \">=3.1\": {\n   *     \"app/*\": [\"./app/types-3.1/*\"],\n   *     \"lib/*\": [\"./lib/types-3.1/*\"]\n   *   },\n   *   \">=3.0\": {\n   *     \"app/*\": [\"./app/types-legacy/*\"],\n   *     \"lib/*\": [\"./lib/types-legacy/*\"]\n   *   }\n   * }\n   * ```\n   *\n   * See the\n   * {@link https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html#version-selection-with-typesversions\n   * | TypeScript documentation} for details.\n   */\n  typesVersions?: Record<string, Record<string, [string, ...string[]]>>;\n\n  /**\n   * The \"exports\" field is used to specify the entry points for a package.\n   * See {@link https://nodejs.org/api/packages.html#exports | Node.js documentation}\n   */\n  // eslint-disable-next-line @rushstack/no-new-null\n  exports?: string | string[] | Record<string, null | string | IPackageJsonExports>;\n\n  /**\n   * The \"files\" field is an array of file globs that should be included in the package during publishing.\n   *\n   * See the {@link https://docs.npmjs.com/cli/v6/configuring-npm/package-json#files | NPM documentation}.\n   */\n  files?: string[];\n}\n\n/**\n * An interface for accessing common fields from a package.json file.\n *\n * @remarks\n * This interface describes a package.json file format whose `name` and `version` field are required.\n * In some situations, the `version` field is optional; in that case, use the {@link INodePackageJson}\n * interface instead.\n *\n * More fields may be added to this interface in the future.  For documentation about the package.json file format,\n * see the {@link http://wiki.commonjs.org/wiki/Packages/1.0 | CommonJS Packages specification}\n * and the {@link https://docs.npmjs.com/files/package.json | NPM manual page}.\n *\n * @public\n */\nexport interface IPackageJson extends INodePackageJson {\n  // Make the \"version\" field non-optional.\n  /** {@inheritDoc INodePackageJson.version} */\n  version: string;\n}\n"]}

package/node_modules/@rushstack/node-core-library/lib/Import.d.ts

@@ -0,0 +1,255 @@
+/**
+ * Common options shared by {@link IImportResolveModuleOptions} and {@link IImportResolvePackageOptions}
+ * @public
+ */
+export interface IImportResolveOptions {
+    /**
+     * The path from which {@link IImportResolveModuleOptions.modulePath} or
+     * {@link IImportResolvePackageOptions.packageName} should be resolved.
+     */
+    baseFolderPath: string;
+    /**
+     * If true, if the package name matches a Node.js system module, then the return
+     * value will be the package name without any path.
+     *
+     * @remarks
+     * This will take precedence over an installed NPM package of the same name.
+     *
+     * Example:
+     * ```ts
+     * // Returns the string "fs" indicating the Node.js system module
+     * Import.resolveModulePath({
+     *   resolvePath: "fs",
+     *   basePath: process.cwd()
+     * })
+     * ```
+     */
+    includeSystemModules?: boolean;
+    /**
+     * If true, then resolvePath is allowed to refer to the package.json of the active project.
+     *
+     * @remarks
+     * This will take precedence over any installed dependency with the same name.
+     * Note that this requires an additional PackageJsonLookup calculation.
+     *
+     * Example:
+     * ```ts
+     * // Returns an absolute path to the current package
+     * Import.resolveModulePath({
+     *   resolvePath: "current-project",
+     *   basePath: process.cwd(),
+     *   allowSelfReference: true
+     * })
+     * ```
+     */
+    allowSelfReference?: boolean;
+    /**
+     * A function used to resolve the realpath of a provided file path.
+     *
+     * @remarks
+     * This is used to resolve symlinks and other non-standard file paths. By default, this uses the
+     * {@link FileSystem.getRealPath} function. However, it can be overridden to use a custom implementation
+     * which may be faster, more accurate, or provide support for additional non-standard file paths.
+     */
+    getRealPath?: (filePath: string) => string;
+}
+/**
+ * Common options shared by {@link IImportResolveModuleAsyncOptions} and {@link IImportResolvePackageAsyncOptions}
+ * @public
+ */
+export interface IImportResolveAsyncOptions extends IImportResolveOptions {
+    /**
+     * A function used to resolve the realpath of a provided file path.
+     *
+     * @remarks
+     * This is used to resolve symlinks and other non-standard file paths. By default, this uses the
+     * {@link FileSystem.getRealPath} function. However, it can be overridden to use a custom implementation
+     * which may be faster, more accurate, or provide support for additional non-standard file paths.
+     */
+    getRealPathAsync?: (filePath: string) => Promise<string>;
+}
+/**
+ * Options for {@link Import.resolveModule}
+ * @public
+ */
+export interface IImportResolveModuleOptions extends IImportResolveOptions {
+    /**
+     * The module identifier to resolve. For example "\@rushstack/node-core-library" or
+     * "\@rushstack/node-core-library/lib/index.js"
+     */
+    modulePath: string;
+}
+/**
+ * Options for {@link Import.resolveModuleAsync}
+ * @public
+ */
+export interface IImportResolveModuleAsyncOptions extends IImportResolveAsyncOptions {
+    /**
+     * The module identifier to resolve. For example "\@rushstack/node-core-library" or
+     * "\@rushstack/node-core-library/lib/index.js"
+     */
+    modulePath: string;
+}
+/**
+ * Options for {@link Import.resolvePackage}
+ * @public
+ */
+export interface IImportResolvePackageOptions extends IImportResolveOptions {
+    /**
+     * The package name to resolve. For example "\@rushstack/node-core-library"
+     */
+    packageName: string;
+    /**
+     * If true, then the module path will be resolved using Node.js's built-in resolution algorithm.
+     *
+     * @remarks
+     * This allows reusing Node's built-in resolver cache.
+     * This implies `allowSelfReference: true`. The passed `getRealPath` will only be used on `baseFolderPath`.
+     */
+    useNodeJSResolver?: boolean;
+}
+/**
+ * Options for {@link Import.resolvePackageAsync}
+ * @public
+ */
+export interface IImportResolvePackageAsyncOptions extends IImportResolveAsyncOptions {
+    /**
+     * The package name to resolve. For example "\@rushstack/node-core-library"
+     */
+    packageName: string;
+}
+/**
+ * Helpers for resolving and importing Node.js modules.
+ * @public
+ */
+export declare class Import {
+    private static __builtInModules;
+    private static get _builtInModules();
+    /**
+     * Provides a way to improve process startup times by lazy-loading imported modules.
+     *
+     * @remarks
+     * This is a more structured wrapper for the {@link https://www.npmjs.com/package/import-lazy|import-lazy}
+     * package.  It enables you to replace an import like this:
+     *
+     * ```ts
+     * import * as example from 'example'; // <-- 100ms load time
+     *
+     * if (condition) {
+     *   example.doSomething();
+     * }
+     * ```
+     *
+     * ...with a pattern like this:
+     *
+     * ```ts
+     * const example: typeof import('example') = Import.lazy('example', require);
+     *
+     * if (condition) {
+     *   example.doSomething(); // <-- 100ms load time occurs here, only if needed
+     * }
+     * ```
+     *
+     * The implementation relies on JavaScript's `Proxy` feature to intercept access to object members.  Thus
+     * it will only work correctly with certain types of module exports.  If a particular export isn't well behaved,
+     * you may need to find (or introduce) some other module in your dependency graph to apply the optimization to.
+     *
+     * Usage guidelines:
+     *
+     * - Always specify types using `typeof` as shown above.
+     *
+     * - Never apply lazy-loading in a way that would convert the module's type to `any`. Losing type safety
+     *   seriously impacts the maintainability of the code base.
+     *
+     * - In cases where the non-runtime types are needed, import them separately using the `Types` suffix:
+     *
+     * ```ts
+     * const example: typeof import('example') = Import.lazy('example', require);
+     * import type * as exampleTypes from 'example';
+     * ```
+     *
+     * - If the imported module confusingly has the same name as its export, then use the Module suffix:
+     *
+     * ```ts
+     * const exampleModule: typeof import('../../logic/Example') = Import.lazy(
+     *   '../../logic/Example', require);
+     * import type * as exampleTypes from '../../logic/Example';
+     * ```
+     *
+     * - If the exports cause a lot of awkwardness (e.g. too many expressions need to have `exampleModule.` inserted
+     *   into them), or if some exports cannot be proxied (e.g. `Import.lazy('example', require)` returns a function
+     *   signature), then do not lazy-load that module.  Instead, apply lazy-loading to some other module which is
+     *   better behaved.
+     *
+     * - It's recommended to sort imports in a standard ordering:
+     *
+     * ```ts
+     * // 1. external imports
+     * import * as path from 'path';
+     * import { Import, JsonFile, JsonObject } from '@rushstack/node-core-library';
+     *
+     * // 2. local imports
+     * import { LocalFile } from './path/LocalFile';
+     *
+     * // 3. lazy-imports (which are technically variables, not imports)
+     * const semver: typeof import('semver') = Import.lazy('semver', require);
+     * ```
+     */
+    static lazy(moduleName: string, require: (id: string) => unknown): any;
+    /**
+     * This resolves a module path using similar logic as the Node.js `require.resolve()` API,
+     * but supporting extra features such as specifying the base folder.
+     *
+     * @remarks
+     * A module path is a text string that might appear in a statement such as
+     * `import { X } from "____";` or `const x = require("___");`.  The implementation is based
+     * on the popular `resolve` NPM package.
+     *
+     * Suppose `example` is an NPM package whose entry point is `lib/index.js`:
+     * ```ts
+     * // Returns "/path/to/project/node_modules/example/lib/index.js"
+     * Import.resolveModule({ modulePath: 'example' });
+     *
+     * // Returns "/path/to/project/node_modules/example/lib/other.js"
+     * Import.resolveModule({ modulePath: 'example/lib/other' });
+     * ```
+     * If you need to determine the containing package folder
+     * (`/path/to/project/node_modules/example`), use {@link Import.resolvePackage} instead.
+     *
+     * @returns the absolute path of the resolved module.
+     * If {@link IImportResolveOptions.includeSystemModules} is specified
+     * and a system module is found, then its name is returned without any file path.
+     */
+    static resolveModule(options: IImportResolveModuleOptions): string;
+    /**
+     * Async version of {@link Import.resolveModule}.
+     */
+    static resolveModuleAsync(options: IImportResolveModuleAsyncOptions): Promise<string>;
+    /**
+     * Performs module resolution to determine the folder where a package is installed.
+     *
+     * @remarks
+     * Suppose `example` is an NPM package whose entry point is `lib/index.js`:
+     * ```ts
+     * // Returns "/path/to/project/node_modules/example"
+     * Import.resolvePackage({ packageName: 'example' });
+     * ```
+     *
+     * If you need to resolve a module path, use {@link Import.resolveModule} instead:
+     * ```ts
+     * // Returns "/path/to/project/node_modules/example/lib/index.js"
+     * Import.resolveModule({ modulePath: 'example' });
+     * ```
+     *
+     * @returns the absolute path of the package folder.
+     * If {@link IImportResolveOptions.includeSystemModules} is specified
+     * and a system module is found, then its name is returned without any file path.
+     */
+    static resolvePackage(options: IImportResolvePackageOptions): string;
+    /**
+     * Async version of {@link Import.resolvePackage}.
+     */
+    static resolvePackageAsync(options: IImportResolvePackageAsyncOptions): Promise<string>;
+    private static _getPackageName;
+}
+//# sourceMappingURL=Import.d.ts.map

package/node_modules/@rushstack/node-core-library/lib/Import.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"Import.d.ts","sourceRoot":"","sources":["../src/Import.ts"],"names":[],"mappings":"AAeA;;;GAGG;AACH,MAAM,WAAW,qBAAqB;IACpC;;;OAGG;IACH,cAAc,EAAE,MAAM,CAAC;IAEvB;;;;;;;;;;;;;;;OAeG;IACH,oBAAoB,CAAC,EAAE,OAAO,CAAC;IAE/B;;;;;;;;;;;;;;;;OAgBG;IACH,kBAAkB,CAAC,EAAE,OAAO,CAAC;IAE7B;;;;;;;OAOG;IACH,WAAW,CAAC,EAAE,CAAC,QAAQ,EAAE,MAAM,KAAK,MAAM,CAAC;CAC5C;AAED;;;GAGG;AACH,MAAM,WAAW,0BAA2B,SAAQ,qBAAqB;IACvE;;;;;;;OAOG;IACH,gBAAgB,CAAC,EAAE,CAAC,QAAQ,EAAE,MAAM,KAAK,OAAO,CAAC,MAAM,CAAC,CAAC;CAC1D;AAED;;;GAGG;AACH,MAAM,WAAW,2BAA4B,SAAQ,qBAAqB;IACxE;;;OAGG;IACH,UAAU,EAAE,MAAM,CAAC;CACpB;AAED;;;GAGG;AACH,MAAM,WAAW,gCAAiC,SAAQ,0BAA0B;IAClF;;;OAGG;IACH,UAAU,EAAE,MAAM,CAAC;CACpB;AAED;;;GAGG;AACH,MAAM,WAAW,4BAA6B,SAAQ,qBAAqB;IACzE;;OAEG;IACH,WAAW,EAAE,MAAM,CAAC;IAEpB;;;;;;OAMG;IACH,iBAAiB,CAAC,EAAE,OAAO,CAAC;CAC7B;AAED;;;GAGG;AACH,MAAM,WAAW,iCAAkC,SAAQ,0BAA0B;IACnF;;OAEG;IACH,WAAW,EAAE,MAAM,CAAC;CACrB;AAOD;;;GAGG;AACH,qBAAa,MAAM;IACjB,OAAO,CAAC,MAAM,CAAC,gBAAgB,CAA0B;IACzD,OAAO,CAAC,MAAM,KAAK,eAAe,GAMjC;IAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OAqEG;WAEW,IAAI,CAAC,UAAU,EAAE,MAAM,EAAE,OAAO,EAAE,CAAC,EAAE,EAAE,MAAM,KAAK,OAAO,GAAG,GAAG;IAK7E;;;;;;;;;;;;;;;;;;;;;;;OAuBG;WACW,aAAa,CAAC,OAAO,EAAE,2BAA2B,GAAG,MAAM;IA4CzE;;OAEG;WACiB,kBAAkB,CAAC,OAAO,EAAE,gCAAgC,GAAG,OAAO,CAAC,MAAM,CAAC;IAwFlG;;;;;;;;;;;;;;;;;;;OAmBG;WACW,cAAc,CAAC,OAAO,EAAE,4BAA4B,GAAG,MAAM;IA6C3E;;OAEG;WACiB,mBAAmB,CAAC,OAAO,EAAE,iCAAiC,GAAG,OAAO,CAAC,MAAM,CAAC;IA8EpG,OAAO,CAAC,MAAM,CAAC,eAAe;CAa/B"}