Pete Bacon Darwin 3788ebb714 fix(ivy): ngcc - don't crash if entry-points have multiple invalid dependencies (#31276) ... If an entry-point has missing dependencies then it cannot be processed and is marked as invalid. Similarly, if an entry-point has dependencies that have been marked as invalid then that entry-point too is invalid. In all these cases, ngcc should quietly ignore these entry-points and continue processing what it can. Previously, if an entry-point had more than one entry-point that was transitively invalid then ngcc was crashing rather than ignoring the entry-point. PR Close #31276		2019-06-26 08:01:43 -07:00
..
commonjs_dependency_host_spec.ts	refactor(ivy): implement a virtual file-system layer in ngtsc + ngcc (#30921)	2019-06-25 16:25:24 -07:00
dependency_resolver_spec.ts	fix(ivy): ngcc - don't crash if entry-points have multiple invalid dependencies (#31276)	2019-06-26 08:01:43 -07:00
esm_dependency_host_spec.ts	refactor(ivy): implement a virtual file-system layer in ngtsc + ngcc (#30921)	2019-06-25 16:25:24 -07:00
module_resolver_spec.ts	refactor(ivy): implement a virtual file-system layer in ngtsc + ngcc (#30921)	2019-06-25 16:25:24 -07:00
umd_dependency_host_spec.ts	refactor(ivy): implement a virtual file-system layer in ngtsc + ngcc (#30921)	2019-06-25 16:25:24 -07:00