George Kalpakas bf682d73d4 fix(ngcc): correctly get config for packages in nested node_modules/ (#37040) ... Previously, ngcc would only be able to match an ngcc configuration to packages that were located inside the project's top-level `node_modules/`. However, if there are multiple versions of a package in a project (e.g. as a transitive dependency of other packages), multiple copies of a package (at different versions) may exist in nested `node_modules/` directories. For example, one at `<project-root>/node_modules/some-package/` and one at `<project-root>/node_modules/other-package/node_modules/some-package/`. In such cases, ngcc was only able to detect the config for the first copy but not for the second. This commit fixes this by returning a new instance of `ProcessedNgccPackageConfig` for each different package path (even if they refer to the same package name). In these `ProcessedNgccPackageConfig`, the `entryPoints` paths have been processed to take the package path into account. PR Close #37040		2020-06-11 18:58:36 -07:00
..
build_marker_spec.ts	build: update license headers to reference Google LLC (#37205)	2020-05-26 14:26:58 -04:00
configuration_spec.ts	fix(ngcc): correctly get config for packages in nested node_modules/ (#37040)	2020-06-11 18:58:36 -07:00
entry_point_bundle_spec.ts	refactor(ngcc): add packageName property to EntryPoint interface (#37040)	2020-06-11 18:58:36 -07:00
entry_point_manifest_spec.ts	fix(ngcc): correctly get config for packages in nested node_modules/ (#37040)	2020-06-11 18:58:36 -07:00
entry_point_spec.ts	fix(ngcc): correctly get config for packages in nested node_modules/ (#37040)	2020-06-11 18:58:36 -07:00