583a9d38a1
Close #35157
In the current version of zone.js, zone.js uses it's own package format, and it is not following the rule
of Angualr package format(APF), so it is not easily to be consumed by Angular CLI or other bundle tools.
For example, zone.js npm package has two bundles,
1. zone.js/dist/zone.js, this is a `es5` bundle.
2. zone.js/dist/zone-evergreen.js, this is a `es2015` bundle.
And Angular CLI has to add some hard-coding code to handle this case, o
|
||
---|---|---|
.. | ||
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