honeymoose/angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/modules/playground
History
Paul Gschwendtner 1d20088291 build: playground examples do not explicitly specify "ng_module" assets (#28562) 
Currently all playground examples are built with NGC, and most
of the HTML resources are automatically inlined. Surprisingly NGC
is able to resolve the relative component assets even though these
aren't specified in the `assets`. This seems to work because NGC
resolves the files in the execroot where the files are present
(if Bazel doesn't use sandboxing).

Issue is tracked with TOOL-667

PR Close #28562
2019-02-13 12:01:54 -08:00
..
e2e_test
fix(ivy): support web worker nodes in unknown property checks (#28610)
2019-02-08 13:35:29 -08:00
src
build: playground examples do not explicitly specify "ng_module" assets (#28562)
2019-02-13 12:01:54 -08:00
BUILD.bazel
build: switch playground examples to bazel (#28490)
2019-02-04 16:51:11 -05:00
favicon.ico
build: adding basic e2e testing infrastructure
2016-05-02 08:15:10 -07:00
README.md
build: switch playground examples to bazel (#28490)
2019-02-04 16:51:11 -05:00
systemjs-config.js
build: switch playground examples to bazel (#28490)
2019-02-04 16:51:11 -05:00
systemjs-rxjs-operators.js
build: switch playground examples to bazel (#28490)
2019-02-04 16:51:11 -05:00
tsconfig-build.json
build: switch playground examples to bazel (#28490)
2019-02-04 16:51:11 -05:00
tsconfig-e2e.json
build: run playground e2e examples with bazel (#28490)
2019-02-04 16:51:11 -05:00

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