Alex Eagle 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
..
e2e	test: cleanup rxjs custom build	2017-05-04 15:07:27 -04:00
src	test: cleanup rxjs custom build	2017-05-04 15:07:27 -04:00
closure.conf	build: update to google-closure-compiler@20171023.0.1 (#20321)	2017-11-10 11:51:57 -08:00
package.json	build: pin ChromeDriver version (#20940)	2017-12-11 15:53:04 -08:00
tsconfig.json	refactor(compiler): don’t always compile `.ngfactory.ts` files by default	2017-06-12 15:27:02 -07:00
yarn.lock	ci: Add back the CLI integration test with pinning (#21555)	2018-01-25 22:18:55 -08:00