angular-cn/packages/compiler-cli/ngcc/test/dependencies
JoostK 4bbf16e654 fix(ngcc): handle deep imports that already have an extension (#32181)
During the dependency analysis phase of ngcc, imports are resolved to
files on disk according to certain module resolution rules. Since module
specifiers are typically missing extensions, or can refer to index.js
barrel files within a directory, the module resolver attempts several
postfixes when searching for a module import on disk. Module  specifiers
that already include an extension, however, would fail to be resolved as
ngcc's module resolver failed to check the location on disk without
adding any postfixes.

Closes #32097

PR Close #32181
2019-08-19 10:12:03 -07:00
..
commonjs_dependency_host_spec.ts fix(ivy): ngcc - resolve `main` property paths correctly (#31509) 2019-07-12 11:37:35 -04:00
dependency_resolver_spec.ts fix(ivy): ngcc - do not consider builtin NodeJS modules as missing (#31872) 2019-08-05 13:06:49 -07:00
esm_dependency_host_spec.ts fix(ivy): ngcc - resolve `main` property paths correctly (#31509) 2019-07-12 11:37:35 -04:00
module_resolver_spec.ts fix(ngcc): handle deep imports that already have an extension (#32181) 2019-08-19 10:12:03 -07:00
umd_dependency_host_spec.ts fix(ivy): ngcc - resolve `main` property paths correctly (#31509) 2019-07-12 11:37:35 -04:00