Paul Gschwendtner adb337c179 build: ensure chromium is not using sandbox within Bazel sandbox for AIO example e2e tests (#49293) ... Chromium is launched via Karma from within the Bazel AIO example e2e tests. This breaks depending on the platform and sandbox mechanism used. We should never use Chromium's sandbox on top of Bazel's sandbox invocation. The Angular CLI exposes a browser exactly for this use-case. PR Close #49293		2023-03-03 19:41:35 +00:00
..
boilerplate	build: ensure chromium is not using sandbox within Bazel sandbox for AIO example e2e tests (#49293)	2023-03-03 19:41:35 +00:00
example-scaffold	build(bazel): incrementally build aio example zips and live examples	2022-11-22 13:51:16 -07:00
.npmrc	build: rely on engines to prevent using npm for dependency install (#41477)	2021-04-07 12:05:01 -07:00
BUILD.bazel	build: always ensure node_modules folders are not picked up in AIO (#48329)	2022-12-02 09:47:43 -08:00
package.json	build: update Angular FW and CLI packages to version 16.0.0-next (#49173)	2023-02-23 10:36:29 -08:00
sync-boilerplate-dependencies.js	build(docs-infra): ensure all boilerplate dependencies are in sync (#47009)	2022-08-02 11:58:51 -07:00
tsconfig.json	build(docs-infra): update docs examples to Angular v12.1.3 (#42949)	2021-08-09 09:41:00 -07:00
yarn.lock	build: update Angular FW and CLI packages to version 16.0.0-next (#49173)	2023-02-23 10:36:29 -08:00