0c344715e5
feat(ivy): expose a series of helpful application inspection tools ( #25919 )
...
PR Close #25919
2018-09-25 09:46:12 -07:00
34ec9244a6
build: update to Node 10 ( #25822 )
...
PR Close #25822
2018-09-06 14:58:30 -07:00
c2b5ebfa24
build: update buildifier to latest ( #24296 )
...
this matches the version in ngcontainer:0.3.1
PR Close #24296
2018-06-12 11:42:35 -07:00
8062f7de9e
test: add i18n to cli-hello-world integration test ( #23527 )
...
PR Close #23527
2018-04-27 07:24:35 -07:00
08fc4f3ad8
build: update to rxjs@6.0.0-tactical-rc.1 ( #23234 )
...
PR Close #23234
2018-04-17 14:09:02 -07:00
6837491f08
test: update cli-hello-world to cli@6.0.0-rc.2 ( #23234 )
...
PR Close #23234
2018-04-17 14:09:02 -07:00
dae4689b1c
test: upgrade cli-hello-world to cli 6.0.0-rc.0 ( #23149 )
...
PR Close #23149
2018-04-04 17:47:47 -07:00
1aebee42eb
test: update cli-hello-world to @angular/cli@1.7.x ( #23149 )
...
PR Close #23149
2018-04-04 17:47:47 -07:00
b43f8bc7d3
feat(core): upgrade rxjs to 6.0.0-alpha.4 ( #22573 )
...
PR Close #22573
2018-03-19 21:51:51 -07:00
8449eb8d62
build: upgrade to TypeScript 2.7 ( #22669 )
...
Fixes : #21571
PR Close #22669
2018-03-12 09:27:23 -07:00
08aa54e1d9
ci: Add back the CLI integration test with pinning ( #21555 )
...
The CLI app is now checked in, rather than generated dynamically with
`ng new`. This loses some assertion power, but gains hermeticity.
It also checks in lock files for all integration tests, avoiding
floating version numbers.
We'll need another place to integration test between changes in
the various repositories - but the angular/angular PR-blocking status
is not the right place to do this.
PR Close #21555
2018-01-25 22:18:55 -08:00
Matias Niemelä
Alex Eagle
Olivier Combe
Igor Minar
Chuck Jazdzewski