George Kalpakas 284af7308b fix(ngcc): do not fail hard when a format-path points to a non-existing or empty file (#40985) ... Previously, when `ngcc` encountered an entry-point with a format-path that pointed to a non-existing or empty file it would throw an error and stop processing the remaining tasks. In the past, we used to ignore such format-paths and continue processing the rest of the tasks ([see code][1]). This was changed to a hard failure in 2954d1b5ca. Looking at the code history, the reason for changing the behavior was an (incorrect) assumption that the condition could not fail. This assumption failed to take into account the case where a 3rd-party library has an invalid format-path in its `package.json`. This is an issue with the library, but it should not prevent `ngcc` from processing other packages/entry-points/formats. This commit fixes this by reporting the task as failed but not throwing an error, thus allowing `ngcc` to continue processing other tasks. [1]: https://github.com/angular/angular/blob/3077c9a1f89c5bd75fb96c16e/packages/compiler-cli/ngcc/src/main.ts#L124 Fixes #40965 PR Close #40985		2021-02-26 08:26:33 -08:00
..
cluster	refactor(compiler-cli): update to use new file-system interfaces (#40281)	2021-01-08 09:34:44 -08:00
tasks	fix(ngcc): do not fail hard when a format-path points to a non-existing or empty file (#40985)	2021-02-26 08:26:33 -08:00
analyze_entry_points.ts	refactor(ngcc): support processing only the typings files of packages (#40976)	2021-02-24 14:23:14 -08:00
api.ts	build: update license headers to reference Google LLC (#37205)	2020-05-26 14:26:58 -04:00
create_compile_function.ts	fix(ngcc): do not fail hard when a format-path points to a non-existing or empty file (#40985)	2021-02-26 08:26:33 -08:00
single_process_executor.ts	refactor(ngcc): move logging code into ngtsc (#37114)	2020-06-22 13:38:47 -07:00