Disable bazel integration test temporarily due to APF v13
test: disable bazel integration test temporarily due to APF v13 (#43431)
Disable bazel integration test temporarily due to APF v13testdisable bazel integration test temporarily due
Committed by devversion
commit message
test: disable bazel integration test temporarily due to APF v13 (#43431)
Temporarily disables the Bazel integration test as it will not
work with the APF v13 output which is strict ESM. We need to
land some logic in `rules_nodejs` first that would allow an
ESM variant of `@angular/compiler-cli` to work.
Once this happened and there is a new release, we can re-enable
the test and make adjustments for v13 APF (i.e. running the linker
plugin when creating the rollup bundles).
PR Close #43431Editor assessment
An exemplary test-infrastructure message. The subject states both action and reason — the bazel integration test is disabled temporarily because of APF v13 — and the body delivers the full engineering context: the new APF output is strict ESM, `rules_nodejs` needs logic that permits an ESM variant of `@angular/compiler-cli`, and once released the test can be re-enabled with linker-plugin adjustments for bundle creation. Constraint, dependency, and exit plan are all documented. Type `test` is accurate; footers are the well-formed `PR Close #43431` trailer. Style is clean — imperative subject, no trailing period, no junk. A reader learns the decision and its roadmap entirely from the message.