6 Commits

Author SHA1 Message Date
George Kalpakas
00c110b055 build: upgrade jasmine (and related typings) to latest version ()
With these changes, the types are a little stricter now and also not
compatible with Protractor's jasmine-like syntax. So, we have to also
use `@types/jasminewd2` for e2e tests (but not for non-e2e tests).

I also had to "augment" `@types/jasminewd2`, because the latest
typings from [DefinitelyTyped][1] do not reflect the fact that the
`jasminewd2` version (v2.1.0) currently used by Protractor supports
passing a `done` callback to a spec.

[1]: 566e039485/types/jasminewd2/index.d.ts (L9-L15)

Fixes 
Closes 

PR Close 
2018-07-06 13:48:02 -07:00
Alex Eagle
c2b5ebfa24 build: update buildifier to latest ()
this matches the version in ngcontainer:0.3.1

PR Close 
2018-06-12 11:42:35 -07:00
Igor Minar
b43f8bc7d3 feat(core): upgrade rxjs to 6.0.0-alpha.4 ()
PR Close 
2018-03-19 21:51:51 -07:00
Alex Eagle
08aa54e1d9 ci: Add back the CLI integration test with pinning ()
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 
2018-01-25 22:18:55 -08:00
George Kalpakas
81d497ce1f build: pin ChromeDriver version ()
Since our version of Chromium is also pinned, a new ChromeDriver (that
drops support for our Chromium version) can cause random (and unrelated
to the corresponding changes) errors on CI.
This commit pins the version of ChromeDriver and it should now be
manually upgraded to a vrsion that is compatible with th currently used
Chromium version.

PR Close 
2017-12-11 15:53:04 -08:00
Olivier Combe
d7a727cc07 feat(platform-browser-dynamic): export JitCompilerFactory ()
Fixes 
PR Close 
2017-11-22 08:56:11 -06:00