angular/packages/compiler-cli/ngcc/test/execution
George Kalpakas d4e949f45c fix(ngcc): cope with packages following APF v14+ (#45833)
In PR #45405, the Angular Package Format (APF) was updated so that
secondary entry-points (such as `@angular/common/http`) do not have
their own `package.json` file, as they used to. Instead, the paths to
their various formats and types are exposed via the primary
`package.json` file's `exports` property. As an example, see the v13
[@angular/common/http/package.json][1] and compare it with the v14
[@angular/common/package.json > exports][2].

Previously, `ngcc` was not able to analyze such v14+ entry-points and
would instead error as it considered such entry-points missing.

This commit addresses the issue by detecting this situation and
synthesizing a `package.json` file for the secondary entry-points based
on the `exports` property of the primary `package.json` file. This data
is only used by `ngcc` in order to determine that the entry-point does
not need further processing, since it is already in Ivy format.

[1]: https://unpkg.com/browse/@angular/common@13.3.5/http/package.json
[2]: https://unpkg.com/browse/@angular/common@14.0.0-next.15/package.json

PR Close #45833
2022-05-06 09:51:14 -07:00
..
cluster fix(ngcc): cope with packages following APF v14+ (#45833) 2022-05-06 09:51:14 -07:00
tasks/queues feat(core): support TypeScript 4.5 (#44164) 2021-11-30 11:59:02 -05:00
helpers.ts feat(core): support TypeScript 4.5 (#44164) 2021-11-30 11:59:02 -05:00
single_processor_executor_spec.ts build: enable useUnknownInCatchVariables (#44679) 2022-02-01 18:17:29 +00:00
utils_spec.ts refactor(ngcc): support processing only the typings files of packages (#40976) 2021-02-24 14:23:14 -08:00