3c7fdc6a9e
Currently the "routing" playground example fails the e2e tests
because it tries to load the OpenSans font using an external
HTTP request. External http requests are not allowed (unless
explicitly enabled) within Bazel in order to ensure that
all targets are built and tested in a hermetic way.
In order to work around this issue in a Bazel idiomatic way,
we just vendor the fonts in the "third_party" folder. Note
that we can technically also enable internet for the RBE
host platform, but it's not a best practice for hermeticity.
The following syntax would allow us to enable internet for
RBE (stated here for tracking)
```
properties: {
name: "dockerNetwork"
value: "standard"
}
```
PR Close #28490
|
||
|---|---|---|
| .. | ||
| e2e_test | ||
| src | ||
| BUILD.bazel | ||
| README.md | ||
| favicon.ico | ||
| systemjs-config.js | ||
| systemjs-rxjs-operators.js | ||
| tsconfig-build.json | ||
| tsconfig-e2e.json | ||
README.md
How to serve the examples
All playground examples are built and served with Bazel. Below is an example that demonstrates how a specific example can be built and served with Bazel:
# e.g. src/zippy_component
yarn bazel run modules/playground/src/zippy_component:devserver
# e.g. src/upgrade
yarn bazel run modules/playground/src/upgrade:devserver