Paul Gschwendtner 634e6662c6 test: update bazel integration test to use linker for v13 APF (#43431) ... As of v13, the package output will be using partial compilation output. This breaks the Bazel setup similar to how it breaks Angular Components. The problem is that `@bazel/concatjs` relies heavily on the UMD files that previously existed in APF, plus it assumed that ngcc pre-processed the files in the `node_modules`. This is no longer the case as there are no UMD files, and the code is not fully-compiled by the Angular compiler. PR Close #43431		2021-10-01 18:28:45 +00:00
..
src	test: update bazel integration test to use linker for v13 APF (#43431)	2021-10-01 18:28:45 +00:00
test/e2e	build: upgrade angular build, integration/bazel and @angular/bazel package to rule_nodejs 2.2.0 (#39182)	2020-10-08 11:54:59 -07:00
tools	build: upgrade angular build, integration/bazel and @angular/bazel package to rule_nodejs 2.2.0 (#39182)	2020-10-08 11:54:59 -07:00
.bazelignore	build: upgrade angular build, integration/bazel and @angular/bazel package to rule_nodejs 2.2.0 (#39182)	2020-10-08 11:54:59 -07:00
.bazelrc	fix(bazel): update build tooling for latest changes in rules_nodejs (#40710)	2021-02-09 10:48:43 -08:00
.bazelversion	fix(bazel): update integration test to use rules_nodejs@3.1.0 (#40710)	2021-02-09 10:48:43 -08:00
BUILD.bazel	test: bazel integration test should use angular npm packages (#28762)	2019-02-19 12:53:19 -08:00
package.json	test: update bazel integration test to use linker for v13 APF (#43431)	2021-10-01 18:28:45 +00:00
protractor.conf.js	feat(bazel): protractor_web_test_suite for release (#24787)	2018-07-12 16:34:45 -04:00
WORKSPACE	build: update bazel setup to latest dev-infra package and rules_nodejs v4.2.0 (#43431)	2021-10-01 18:28:41 +00:00
yarn.lock	test: update bazel integration test to use linker for v13 APF (#43431)	2021-10-01 18:28:45 +00:00