Paul Gschwendtner 56ff04607c build: re-enable linker compliance tests (#53571) ... The linker compliance tests were disabled with a Babel update and nobody realized for quite a while, via https://github.com/angular/angular/pull/49914. As we've came across this lost coverage, which also is quite impactful as all libraries depend on linked output- I've took initiative to debug the root cause as there was no follow-up. https://github.com/angular/angular/issues/51647. It turned out to be a highly complex issue that is non-trivial to fix, but at least we should try to resurrect the significant portion of test coverage by still running the linker tests- avoiding regressions, or unexpected issues (like with defer being developed). We can work on re-enabling and fixing source-maps separately. Tracked via https://github.com/angular/angular/issues/51647. PR Close #53571		2024-01-04 12:07:13 -08:00
..
BUILD.bazel	build: re-enable linker compliance tests (#53571)	2024-01-04 12:07:13 -08:00
linked_compile_spec.ts	build: re-enable linker compliance tests (#53571)	2024-01-04 12:07:13 -08:00