<!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> ## Current Behavior <!-- This is the behavior we have today --> We only ever discover one version of an external dependency for the file-map.json. This means the `@nx/dependency-checks` lint rule can produce incorrect failures when multiple copies of a dependency exist within a workspace. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> In the file-map.json the project specific version of a package (if multiple exist) is preferred and therefore the lint rule produces accurate results. --- For example, in a repo where the root package.json has lodash@4.0.0 (which becomes `npm:lodash` on graph) and the foo project has lodash@3.0.0: **Before**  **After**  ## Performance `NX_ISOLATE_PLUGINS=true NX_PERF_LOGGING=true NX_DAEMON=false nx show project nx --json false` ** Before ** Time for 'build typescript dependencies' 505.52144700009376 ** After ** Time for 'build typescript dependencies' 701.247584999539
14 lines
615 B
TypeScript
14 lines
615 B
TypeScript
export { resolveModuleByImport } from './utils/typescript/ast-utils';
|
|
// eslint-disable-next-line @typescript-eslint/no-restricted-imports
|
|
export {
|
|
registerTsProject,
|
|
registerTsConfigPaths,
|
|
} from 'nx/src/plugins/js/utils/register';
|
|
// eslint-disable-next-line @typescript-eslint/no-restricted-imports
|
|
export {
|
|
TargetProjectLocator,
|
|
isBuiltinModuleImport,
|
|
} from 'nx/src/plugins/js/project-graph/build-dependencies/target-project-locator';
|
|
// eslint-disable-next-line @typescript-eslint/no-restricted-imports
|
|
export { findProjectsNpmDependencies } from 'nx/src/plugins/js/package-json/create-package-json';
|