From f355be267fc59a116a9f697c0163f4f2e8c5e45b Mon Sep 17 00:00:00 2001 From: Nikolas Komonen <118216176+nkomonen-amazon@users.noreply.github.com> Date: Mon, 8 Jan 2024 14:50:35 -0500 Subject: [PATCH] dev: Add dependency diagram utility (#4234) Adding in this dependency diagram generating utility for toolkit Browser work since we can have transitive dependencies which break the toolkit from running in the Browser. This will help us to find dependencies more easily instead of manually searching. Signed-off-by: nkomonen --- .dependency-cruiser.js | 466 +++++++++++++++ .gitignore | 3 + docs/browser.md | 21 + docs/images/dependency-graph-small.svg | 90 +++ docs/images/dependency-graph.svg | 768 +++++++++++++++++++++++++ 5 files changed, 1348 insertions(+) create mode 100644 .dependency-cruiser.js create mode 100644 docs/images/dependency-graph-small.svg create mode 100644 docs/images/dependency-graph.svg diff --git a/.dependency-cruiser.js b/.dependency-cruiser.js new file mode 100644 index 00000000000..1976385c872 --- /dev/null +++ b/.dependency-cruiser.js @@ -0,0 +1,466 @@ +/** + * This file was generated using the `dependency-cruiser` npm package. + * + * The initial purpose for this file is to find transitive dependencies for Browser + * incompatible modules (eg `fs-extra`). See `browser.md` explaining how this is used. + */ + +/** @type {import('dependency-cruiser').IConfiguration} */ +module.exports = { + forbidden: [ + { + name: 'no-circular', + severity: 'warn', + comment: + 'This dependency is part of a circular relationship. You might want to revise ' + + 'your solution (i.e. use dependency inversion, make sure the modules have a single responsibility) ', + from: {}, + to: { + circular: true, + }, + }, + { + name: 'no-orphans', + comment: + "This is an orphan module - it's likely not used (anymore?). Either use it or " + + "remove it. If it's logical this module is an orphan (i.e. it's a config file), " + + 'add an exception for it in your dependency-cruiser configuration. By default ' + + 'this rule does not scrutinize dot-files (e.g. .eslintrc.js), TypeScript declaration ' + + 'files (.d.ts), tsconfig.json and some of the babel and webpack configs.', + severity: 'warn', + from: { + orphan: true, + pathNot: [ + '(^|/)[.][^/]+[.](js|cjs|mjs|ts|json)$', // dot files + '[.]d[.]ts$', // TypeScript declaration files + '(^|/)tsconfig[.]json$', // TypeScript config + '(^|/)(babel|webpack)[.]config[.](js|cjs|mjs|ts|json)$', // other configs + ], + }, + to: {}, + }, + { + name: 'no-deprecated-core', + comment: + 'A module depends on a node core module that has been deprecated. Find an alternative - these are ' + + "bound to exist - node doesn't deprecate lightly.", + severity: 'warn', + from: {}, + to: { + dependencyTypes: ['core'], + path: [ + '^(v8/tools/codemap)$', + '^(v8/tools/consarray)$', + '^(v8/tools/csvparser)$', + '^(v8/tools/logreader)$', + '^(v8/tools/profile_view)$', + '^(v8/tools/profile)$', + '^(v8/tools/SourceMap)$', + '^(v8/tools/splaytree)$', + '^(v8/tools/tickprocessor-driver)$', + '^(v8/tools/tickprocessor)$', + '^(node-inspect/lib/_inspect)$', + '^(node-inspect/lib/internal/inspect_client)$', + '^(node-inspect/lib/internal/inspect_repl)$', + '^(async_hooks)$', + '^(punycode)$', + '^(domain)$', + '^(constants)$', + '^(sys)$', + '^(_linklist)$', + '^(_stream_wrap)$', + ], + }, + }, + { + name: 'not-to-deprecated', + comment: + 'This module uses a (version of an) npm module that has been deprecated. Either upgrade to a later ' + + 'version of that module, or find an alternative. Deprecated modules are a security risk.', + severity: 'warn', + from: {}, + to: { + dependencyTypes: ['deprecated'], + }, + }, + { + name: 'no-non-package-json', + severity: 'error', + comment: + "This module depends on an npm package that isn't in the 'dependencies' section of your package.json. " + + "That's problematic as the package either (1) won't be available on live (2 - worse) will be " + + 'available on live with an non-guaranteed version. Fix it by adding the package to the dependencies ' + + 'in your package.json.', + from: {}, + to: { + dependencyTypes: ['npm-no-pkg', 'npm-unknown'], + }, + }, + { + name: 'not-to-unresolvable', + comment: + "This module depends on a module that cannot be found ('resolved to disk'). If it's an npm " + + 'module: add it to your package.json. In all other cases you likely already know what to do.', + severity: 'error', + from: {}, + to: { + couldNotResolve: true, + }, + }, + { + name: 'no-duplicate-dep-types', + comment: + "Likely this module depends on an external ('npm') package that occurs more than once " + + 'in your package.json i.e. bot as a devDependencies and in dependencies. This will cause ' + + 'maintenance problems later on.', + severity: 'warn', + from: {}, + to: { + moreThanOneDependencyType: true, + // as it's pretty common to have a type import be a type only import + // _and_ (e.g.) a devDependency - don't consider type-only dependency + // types for this rule + dependencyTypesNot: ['type-only'], + }, + }, + + /* rules you might want to tweak for your specific situation: */ + + { + name: 'not-to-spec', + comment: + 'This module depends on a spec (test) file. The sole responsibility of a spec file is to test code. ' + + "If there's something in a spec that's of use to other modules, it doesn't have that single " + + 'responsibility anymore. Factor it out into (e.g.) a separate utility/ helper or a mock.', + severity: 'error', + from: {}, + to: { + path: '[.](spec|test)[.](js|mjs|cjs|ts|ls|coffee|litcoffee|coffee[.]md)$', + }, + }, + { + name: 'not-to-dev-dep', + severity: 'error', + comment: + "This module depends on an npm package from the 'devDependencies' section of your " + + 'package.json. It looks like something that ships to production, though. To prevent problems ' + + "with npm packages that aren't there on production declare it (only!) in the 'dependencies'" + + 'section of your package.json. If this module is development only - add it to the ' + + 'from.pathNot re of the not-to-dev-dep rule in the dependency-cruiser configuration', + from: { + path: '^(src)', + pathNot: '[.](spec|test)[.](js|mjs|cjs|ts|ls|coffee|litcoffee|coffee[.]md)$', + }, + to: { + dependencyTypes: ['npm-dev'], + // type only dependencies are not a problem as they don't end up in the + // production code or are ignored by the runtime. + dependencyTypesNot: ['type-only'], + pathNot: ['node_modules/@types/'], + }, + }, + { + name: 'optional-deps-used', + severity: 'info', + comment: + 'This module depends on an npm package that is declared as an optional dependency ' + + "in your package.json. As this makes sense in limited situations only, it's flagged here. " + + "If you're using an optional dependency here by design - add an exception to your" + + 'dependency-cruiser configuration.', + from: {}, + to: { + dependencyTypes: ['npm-optional'], + }, + }, + { + name: 'peer-deps-used', + comment: + 'This module depends on an npm package that is declared as a peer dependency ' + + 'in your package.json. This makes sense if your package is e.g. a plugin, but in ' + + 'other cases - maybe not so much. If the use of a peer dependency is intentional ' + + 'add an exception to your dependency-cruiser configuration.', + severity: 'warn', + from: {}, + to: { + dependencyTypes: ['npm-peer'], + }, + }, + ], + options: { + /* conditions specifying which files not to follow further when encountered: + - path: a regular expression to match + - dependencyTypes: see https://github.com/sverweij/dependency-cruiser/blob/main/doc/rules-reference.md#dependencytypes-and-dependencytypesnot + for a complete list + */ + doNotFollow: { + path: 'node_modules', + }, + + /* conditions specifying which dependencies to exclude + - path: a regular expression to match + - dynamic: a boolean indicating whether to ignore dynamic (true) or static (false) dependencies. + leave out if you want to exclude neither (recommended!) + */ + // exclude : { + // path: '', + // dynamic: true + // }, + + /* pattern specifying which files to include (regular expression) + dependency-cruiser will skip everything not matching this pattern + */ + // includeOnly : '', + + /* dependency-cruiser will include modules matching against the focus + regular expression in its output, as well as their neighbours (direct + dependencies and dependents) + */ + // focus : '', + + /* List of module systems to cruise. + When left out dependency-cruiser will fall back to the list of _all_ + module systems it knows of. It's the default because it's the safe option + It might come at a performance penalty, though. + moduleSystems: ['amd', 'cjs', 'es6', 'tsd'] + + As in practice only commonjs ('cjs') and ecmascript modules ('es6') + are widely used, you can limit the moduleSystems to those. + */ + + // moduleSystems: ['cjs', 'es6'], + + /* prefix for links in html and svg output (e.g. 'https://github.com/you/yourrepo/blob/develop/' + to open it on your online repo or `vscode://file/${process.cwd()}/` to + open it in visual studio code), + */ + // prefix: '', + + /* false (the default): ignore dependencies that only exist before typescript-to-javascript compilation + true: also detect dependencies that only exist before typescript-to-javascript compilation + "specify": for each dependency identify whether it only exists before compilation or also after + */ + // tsPreCompilationDeps: false, + + /* + list of extensions to scan that aren't javascript or compile-to-javascript. + Empty by default. Only put extensions in here that you want to take into + account that are _not_ parsable. + */ + // extraExtensionsToScan: [".json", ".jpg", ".png", ".svg", ".webp"], + + /* if true combines the package.jsons found from the module up to the base + folder the cruise is initiated from. Useful for how (some) mono-repos + manage dependencies & dependency definitions. + */ + // combinedDependencies: false, + + /* if true leave symlinks untouched, otherwise use the realpath */ + // preserveSymlinks: false, + + /* TypeScript project file ('tsconfig.json') to use for + (1) compilation and + (2) resolution (e.g. with the paths property) + + The (optional) fileName attribute specifies which file to take (relative to + dependency-cruiser's current working directory). When not provided + defaults to './tsconfig.json'. + */ + tsConfig: { + fileName: 'tsconfig.json', + }, + + /* Webpack configuration to use to get resolve options from. + + The (optional) fileName attribute specifies which file to take (relative + to dependency-cruiser's current working directory. When not provided defaults + to './webpack.conf.js'. + + The (optional) `env` and `arguments` attributes contain the parameters to be passed if + your webpack config is a function and takes them (see webpack documentation + for details) + */ + // webpackConfig: { + // fileName: 'webpack.config.js', + // env: {}, + // arguments: {} + // }, + + /* Babel config ('.babelrc', '.babelrc.json', '.babelrc.json5', ...) to use + for compilation (and whatever other naughty things babel plugins do to + source code). This feature is well tested and usable, but might change + behavior a bit over time (e.g. more precise results for used module + systems) without dependency-cruiser getting a major version bump. + */ + // babelConfig: { + // fileName: '.babelrc', + // }, + + /* List of strings you have in use in addition to cjs/ es6 requires + & imports to declare module dependencies. Use this e.g. if you've + re-declared require, use a require-wrapper or use window.require as + a hack. + */ + // exoticRequireStrings: [], + /* options to pass on to enhanced-resolve, the package dependency-cruiser + uses to resolve module references to disk. You can set most of these + options in a webpack.conf.js - this section is here for those + projects that don't have a separate webpack config file. + + Note: settings in webpack.conf.js override the ones specified here. + */ + enhancedResolveOptions: { + /* List of strings to consider as 'exports' fields in package.json. Use + ['exports'] when you use packages that use such a field and your environment + supports it (e.g. node ^12.19 || >=14.7 or recent versions of webpack). + + If you have an `exportsFields` attribute in your webpack config, that one + will have precedence over the one specified here. + */ + exportsFields: ['exports'], + /* List of conditions to check for in the exports field. e.g. use ['imports'] + if you're only interested in exposed es6 modules, ['require'] for commonjs, + or all conditions at once `(['import', 'require', 'node', 'default']`) + if anything goes for you. Only works when the 'exportsFields' array is + non-empty. + + If you have a 'conditionNames' attribute in your webpack config, that one will + have precedence over the one specified here. + */ + conditionNames: ['import', 'require', 'node', 'default'], + /* + The extensions, by default are the same as the ones dependency-cruiser + can access (run `npx depcruise --info` to see which ones that are in + _your_ environment. If that list is larger than what you need (e.g. + it contains .js, .jsx, .ts, .tsx, .cts, .mts - but you don't use + TypeScript you can pass just the extensions you actually use (e.g. + [".js", ".jsx"]). This can speed up the most expensive step in + dependency cruising (module resolution) quite a bit. + */ + // extensions: [".js", ".jsx", ".ts", ".tsx", ".d.ts"], + /* + If your TypeScript project makes use of types specified in 'types' + fields in package.jsons of external dependencies, specify "types" + in addition to "main" in here, so enhanced-resolve (the resolver + dependency-cruiser uses) knows to also look there. You can also do + this if you're not sure, but still use TypeScript. In a future version + of dependency-cruiser this will likely become the default. + */ + mainFields: ['main', 'types', 'typings'], + /* + A list of alias fields in manifests (package.jsons). + Specify a field, such as browser, to be parsed according to + [this specification](https://github.com/defunctzombie/package-browser-field-spec). + Also see [resolve.alias](https://webpack.js.org/configuration/resolve/#resolvealiasfields) + in the webpack docs. + + Defaults to an empty array (don't use any alias fields). + */ + // aliasFields: ["browser"], + }, + reporterOptions: { + dot: { + /* pattern of modules that can be consolidated in the detailed + graphical dependency graph. The default pattern in this configuration + collapses everything in node_modules to one folder deep so you see + the external modules, but not the innards your app depends upon. + */ + collapsePattern: 'node_modules/(@[^/]+/[^/]+|[^/]+)', + + /* Options to tweak the appearance of your graph.See + https://github.com/sverweij/dependency-cruiser/blob/main/doc/options-reference.md#reporteroptions + for details and some examples. If you don't specify a theme + don't worry - dependency-cruiser will fall back to the default one. + */ + // theme: { + // graph: { + // /* use splines: "ortho" for straight lines. Be aware though + // graphviz might take a long time calculating ortho(gonal) + // routings. + // */ + // splines: "true" + // }, + // modules: [ + // { + // criteria: { matchesFocus: true }, + // attributes: { + // fillcolor: "lime", + // penwidth: 2, + // }, + // }, + // { + // criteria: { matchesFocus: false }, + // attributes: { + // fillcolor: "lightgrey", + // }, + // }, + // { + // criteria: { matchesReaches: true }, + // attributes: { + // fillcolor: "lime", + // penwidth: 2, + // }, + // }, + // { + // criteria: { matchesReaches: false }, + // attributes: { + // fillcolor: "lightgrey", + // }, + // }, + // { + // criteria: { source: "^src/model" }, + // attributes: { fillcolor: "#ccccff" } + // }, + // { + // criteria: { source: "^src/view" }, + // attributes: { fillcolor: "#ccffcc" } + // }, + // ], + // dependencies: [ + // { + // criteria: { "rules[0].severity": "error" }, + // attributes: { fontcolor: "red", color: "red" } + // }, + // { + // criteria: { "rules[0].severity": "warn" }, + // attributes: { fontcolor: "orange", color: "orange" } + // }, + // { + // criteria: { "rules[0].severity": "info" }, + // attributes: { fontcolor: "blue", color: "blue" } + // }, + // { + // criteria: { resolved: "^src/model" }, + // attributes: { color: "#0000ff77" } + // }, + // { + // criteria: { resolved: "^src/view" }, + // attributes: { color: "#00770077" } + // } + // ] + // } + }, + archi: { + /* pattern of modules that can be consolidated in the high level + graphical dependency graph. If you use the high level graphical + dependency graph reporter (`archi`) you probably want to tweak + this collapsePattern to your situation. + */ + collapsePattern: + '^(packages|src|lib|app|bin|test(s?)|spec(s?))/[^/]+|node_modules/(@[^/]+/[^/]+|[^/]+)', + + /* Options to tweak the appearance of your graph.See + https://github.com/sverweij/dependency-cruiser/blob/main/doc/options-reference.md#reporteroptions + for details and some examples. If you don't specify a theme + for 'archi' dependency-cruiser will use the one specified in the + dot section (see above), if any, and otherwise use the default one. + */ + // theme: { + // }, + }, + text: { + highlightFocused: true, + }, + }, + }, +} +// generated: dependency-cruiser@16.0.0 on 2024-01-05T15:20:51.138Z diff --git a/.gitignore b/.gitignore index 52921740533..2cc887953d7 100644 --- a/.gitignore +++ b/.gitignore @@ -14,6 +14,9 @@ README.quickstart.vscode.md .gitcommit resources/debugger/__pycache__ +# Generated if running the `depcruise` command from the documentation example +/dependency-graph.svg + # Auto generated definitions src/**/*.gen.ts src.gen/* diff --git a/docs/browser.md b/docs/browser.md index 20518a1dff7..7a399725c6c 100644 --- a/docs/browser.md +++ b/docs/browser.md @@ -57,3 +57,24 @@ To get to the AWS Toolkit logs: 1. Open Command Palette: `cmd/ctrl` + `shift` + `p` 2. Type: `AWS: View Toolkit Logs` + +## Finding incompatible transitive dependencies + +For example, if I have a Typescript module, `myFile.ts`, that imports a module, which imports another module (transitive dependency) such as `fs-extra`, +when I execute `myFile.ts` in the browser it will break due to `fs-extra` not being browser compatible. + +It may be difficult to determine which module imported `fs-extra` due to a nested chain of transitive dependencies. + +As a solution, we can use [`dependency-cruiser`](https://www.npmjs.com/package/dependency-cruiser) to generate a dependency diagram +to help us visualize the imports and determine which module is importing a certain module. + +### How to use + +1. Install the `graphiz` cli, this provides the `dot` cli command + - Mac: `brew install graphiz` + - Others: [See documentation](https://www.graphviz.org/download/) +2. Run `npx depcruise {RELATIVE_PATH_TO_FILE} --output-type dot | dot -T svg > dependency-graph.svg` + - For example, `npx depcruise src/srcShared/fs.ts --output-type dot | dot -T svg > dependency-graph.svg` generates the following which shows `fs-extra` is imported by `fileSystemUtilities.ts`: + ![Dependency Graph](./images/dependency-graph.svg) + - Additionally specify a certain dependency with `--reaches` , `npx depcruise src/srcShared/fs.ts --reaches "fs-extra" --output-type dot | dot -T svg > dependency-graph.svg`, to hide unrelated dependencies: + ![Dependency Graph](./images/dependency-graph-small.svg) diff --git a/docs/images/dependency-graph-small.svg b/docs/images/dependency-graph-small.svg new file mode 100644 index 00000000000..30c43a4bb80 --- /dev/null +++ b/docs/images/dependency-graph-small.svg @@ -0,0 +1,90 @@ + + + + + + +dependency-cruiser output + + +cluster_node_modules + +node_modules + + +cluster_src + +src + + +cluster_src/shared + +shared + + +cluster_src/srcShared + +srcShared + + + +node_modules/fs-extra + + + + + +fs-extra + + + + + +src/shared/extensionUtilities.ts + + +extensionUtilities.ts + + + + + +src/shared/filesystemUtilities.ts + + +filesystemUtilities.ts + + + + + +src/shared/extensionUtilities.ts->src/shared/filesystemUtilities.ts + + + + + +src/shared/filesystemUtilities.ts->node_modules/fs-extra + + + + + +src/srcShared/fs.ts + + +fs.ts + + + + + +src/srcShared/fs.ts->src/shared/extensionUtilities.ts + + + + + diff --git a/docs/images/dependency-graph.svg b/docs/images/dependency-graph.svg new file mode 100644 index 00000000000..c8e520907a4 --- /dev/null +++ b/docs/images/dependency-graph.svg @@ -0,0 +1,768 @@ + + + + + + +dependency-cruiser output + + +cluster_node_modules + +node_modules + + +cluster_node_modules/@aws-sdk + +@aws-sdk + + +cluster_node_modules/@types + +@types + + +cluster_src + +src + + +cluster_src/shared + +shared + + +cluster_src/shared/clients + +clients + + +cluster_src/shared/logger + +logger + + +cluster_src/shared/templates + +templates + + +cluster_src/shared/utilities + +utilities + + +cluster_src/shared/vscode + +vscode + + +cluster_src/srcShared + +srcShared + + + +crypto + + +crypto + + + + + +fs + + +fs + + + + + +node_modules/@aws-sdk/service-error-classification + + + + + +service-error-classification + + + + + +node_modules/@aws-sdk/smithy-client + + + + + +smithy-client + + + + + +node_modules/@types/vscode + + + + + +vscode + + + + + +node_modules/aws-sdk + + + + + +aws-sdk + + + + + +node_modules/fs-extra + + + + + +fs-extra + + + + + +node_modules/lodash + + + + + +lodash + + + + + +node_modules/semver + + + + + +semver + + + + + +node_modules/vscode-nls + + + + + +vscode-nls + + + + + +os + + +os + + + + + +package.json + + +package.json + + + + + +path + + +path + + + + + +src/shared/clients/ec2MetadataClient.ts + + +ec2MetadataClient.ts + + + + + +src/shared/clients/ec2MetadataClient.ts->node_modules/aws-sdk + + + + + +src/shared/errors.ts + + +errors.ts + + + + + +src/shared/errors.ts->node_modules/@aws-sdk/service-error-classification + + + + + +no-non-package-json + + + +src/shared/errors.ts->node_modules/@aws-sdk/smithy-client + + + + + +src/shared/errors.ts->node_modules/@types/vscode + + + + + +src/shared/utilities/timeoutUtils.ts + + +timeoutUtils.ts + + + + + +src/shared/errors.ts->src/shared/utilities/timeoutUtils.ts + + + + + +src/shared/utilities/tsUtils.ts + + +tsUtils.ts + + + + + +src/shared/errors.ts->src/shared/utilities/tsUtils.ts + + + + + +src/shared/utilities/timeoutUtils.ts->node_modules/@types/vscode + + + + + +src/shared/extensionGlobals.ts + + +extensionGlobals.ts + + + + + +src/shared/utilities/timeoutUtils.ts->src/shared/extensionGlobals.ts + + + + + +src/shared/extensionUtilities.ts + + +extensionUtilities.ts + + + + + +src/shared/extensionUtilities.ts->node_modules/@types/vscode + + + + + +src/shared/extensionUtilities.ts->node_modules/lodash + + + + + +src/shared/extensionUtilities.ts->node_modules/vscode-nls + + + + + +src/shared/extensionUtilities.ts->os + + + + + +src/shared/extensionUtilities.ts->path + + + + + +src/shared/extensionUtilities.ts->src/shared/clients/ec2MetadataClient.ts + + + + + +src/shared/extensions.ts + + +extensions.ts + + + + + +src/shared/extensionUtilities.ts->src/shared/extensions.ts + + + + + +src/shared/filesystemUtilities.ts + + +filesystemUtilities.ts + + + + + +src/shared/extensionUtilities.ts->src/shared/filesystemUtilities.ts + + + + + +src/shared/logger/index.ts + + +index.ts + + + + + +src/shared/extensionUtilities.ts->src/shared/logger/index.ts + + + + + +src/shared/settings.ts + + +settings.ts + + + + + +src/shared/extensionUtilities.ts->src/shared/settings.ts + + + + + +src/shared/templates/baseTemplates.ts + + +baseTemplates.ts + + + + + +src/shared/extensionUtilities.ts->src/shared/templates/baseTemplates.ts + + + + + +src/shared/vscode/env.ts + + +env.ts + + + + + +src/shared/extensionUtilities.ts->src/shared/vscode/env.ts + + + + + +src/shared/filesystemUtilities.ts->crypto + + + + + +src/shared/filesystemUtilities.ts->fs + + + + + +src/shared/filesystemUtilities.ts->node_modules/@types/vscode + + + + + +src/shared/filesystemUtilities.ts->node_modules/fs-extra + + + + + +src/shared/filesystemUtilities.ts->os + + + + + +src/shared/filesystemUtilities.ts->path + + + + + +src/shared/filesystemUtilities.ts->src/shared/extensionGlobals.ts + + + + + +src/shared/filesystemUtilities.ts->src/shared/logger/index.ts + + + + + +src/shared/globalState.ts + + +globalState.ts + + + + + +src/shared/filesystemUtilities.ts->src/shared/globalState.ts + + + + + +src/shared/utilities/pathUtils.ts + + +pathUtils.ts + + + + + +src/shared/filesystemUtilities.ts->src/shared/utilities/pathUtils.ts + + + + + +src/shared/logger/logger.ts + + +logger.ts + + + + + +src/shared/logger/index.ts->src/shared/logger/logger.ts + + + + + +src/shared/logger/outputChannel.ts + + +outputChannel.ts + + + + + +src/shared/logger/index.ts->src/shared/logger/outputChannel.ts + + + + + +src/shared/settings.ts->node_modules/@types/vscode + + + + + +src/shared/settings.ts->package.json + + + + + +src/shared/settings.ts->src/shared/errors.ts + + + + + +src/shared/settings.ts->src/shared/utilities/tsUtils.ts + + + + + +src/shared/settings.ts->src/shared/logger/index.ts + + + + + +src/shared/settings.ts->src/shared/vscode/env.ts + + + + + +src/shared/utilities/collectionUtils.ts + + +collectionUtils.ts + + + + + +src/shared/settings.ts->src/shared/utilities/collectionUtils.ts + + + + + +src/shared/utilities/functionUtils.ts + + +functionUtils.ts + + + + + +src/shared/settings.ts->src/shared/utilities/functionUtils.ts + + + + + +src/shared/utilities/typeConstructors.ts + + +typeConstructors.ts + + + + + +src/shared/settings.ts->src/shared/utilities/typeConstructors.ts + + + + + +src/shared/vscode/env.ts->node_modules/@types/vscode + + + + + +src/shared/vscode/env.ts->node_modules/semver + + + + + +src/shared/vscode/env.ts->package.json + + + + + +src/shared/globalState.ts->node_modules/@types/vscode + + + + + +src/shared/globalState.ts->src/shared/extensionGlobals.ts + + + + + +src/shared/globalState.ts->src/shared/logger/logger.ts + + + + + +src/shared/utilities/pathUtils.ts->os + + + + + +src/shared/utilities/pathUtils.ts->path + + + + + +src/shared/logger/logger.ts->src/shared/extensionGlobals.ts + + + + + +src/shared/logger/outputChannel.ts->node_modules/@types/vscode + + + + + +src/shared/utilities/collectionUtils.ts->src/shared/utilities/tsUtils.ts + + + + + +src/shared/utilities/asyncCollection.ts + + +asyncCollection.ts + + + + + +src/shared/utilities/collectionUtils.ts->src/shared/utilities/asyncCollection.ts + + + + + +src/shared/utilities/functionUtils.ts->src/shared/extensionGlobals.ts + + + + + +src/shared/utilities/typeConstructors.ts->src/shared/utilities/tsUtils.ts + + + + + +src/shared/utilities/typeConstructors.ts->src/shared/vscode/env.ts + + + + + +src/shared/utilities/asyncCollection.ts->src/shared/utilities/tsUtils.ts + + + + + +src/srcShared/fs.ts + + +fs.ts + + + + + +src/srcShared/fs.ts->fs + + + + + +src/srcShared/fs.ts->node_modules/@types/vscode + + + + + +src/srcShared/fs.ts->src/shared/errors.ts + + + + + +src/srcShared/fs.ts->src/shared/extensionUtilities.ts + + + + +