d2b64cc008
build(bazel): revert back to yarn 1.12.1 under Bazel to fix Windows file-in-use issues ( #29431 )
...
PR Close #29431
2019-03-20 18:36:13 -04:00
b460b26308
build(bazel): update to nodejs rules 0.27.7 ( #29375 )
...
PR Close #29375
2019-03-19 23:39:37 -04:00
ea0e832e5f
build(bazel): update to nodejs rules 0.27.6 ( #29375 )
...
PR Close #29375
2019-03-19 23:39:36 -04:00
fc8048ddaf
build: update to nodejs rules 0.27 ( #29210 )
...
PR Close #29210
2019-03-14 19:35:00 -07:00
b2aadffbbc
revert: build: update to nodejs rules 0.27 ( #29210 )
...
This reverts commit 08231f0bfa
2019-03-14 17:38:35 -07:00
6ab8c0b371
build(bazel): update bazel managed yarn to 1.13.0 (same as CI version) ( #29311 )
...
PR Close #29311
2019-03-14 16:01:35 -04:00
08231f0bfa
build: update to nodejs rules 0.27 ( #29210 )
...
PR Close #29210
2019-03-14 11:38:12 -04:00
75748d6044
feat: add support for TypeScript 3.3 (and drop older versions) ( #29004 )
...
https://blogs.msdn.microsoft.com/typescript/2019/01/31/announcing-typescript-3-3/
BREAKING CHANGE: TypeScript 3.1 and 3.2 are no longer supported.
Please update your TypeScript version to 3.3
PR Close #29004
2019-03-13 10:38:37 -07:00
ba602dbaec
build: update Bazel to 0.23 ( #29058 )
...
PR Close #29058
2019-03-01 15:24:05 -08:00
9fe522f3e2
build: yarn.lock updates ( #28871 )
...
PR Close #28871
2019-02-28 12:06:36 -08:00
ea09430039
build: rules_nodejs 0.26.0 & use @npm instead of @ngdeps now that downstream angular build uses angular bundles ( #28871 )
...
PR Close #28871
2019-02-28 12:06:36 -08:00
dad5a258b8
style: enforce buildifier lint on CI ( #28186 )
...
PR Close #28186
2019-02-26 16:57:41 -08:00
ce68b4d839
style: enforce buildifier lint on CI ( #28186 )
...
PR Close #28186
2019-02-26 16:57:41 -08:00
350802b207
build: update to latest bazel rules ( #28931 )
...
PR Close #28931
2019-02-22 17:27:09 -08:00
f4d652568d
build: use uname instead of relying on sed --version ( #28900 )
...
PR Close #28900
2019-02-21 17:49:17 -08:00
3cc9ba24c6
build: fix integration/bazel on OSX and update integration yarn.lock files ( #28900 )
...
PR Close #28900
2019-02-21 17:49:17 -08:00
ebffde7143
build: update to rules_typescript 0.25.1 ( #28625 )
...
Updated a spot in the compiler which assumed es5 downlevelling get ready for es2015 devmode in the future.
PR Close #28625
2019-02-21 07:46:21 -08:00
1eccf64b15
build: Add .bzl/BUILD files to @angular/bazel package ( #28769 )
...
It's now possible to use it as a hybrid package in latest rules_nodejs, so no WORKSPACE dep is needed
PR Close #28769
2019-02-19 17:55:57 -08:00
02ee8c7bc5
build: fix inflight PR conflict in integration/bazel ( #28720 )
...
PR Close #28720
2019-02-19 16:28:14 -08:00
25aae64274
build(bazel): do not build rxjs from source under Bazel ( #28720 )
...
PR Close #28720
2019-02-19 16:28:14 -08:00
a834c745d7
test: bazel integration test should use angular npm packages ( #28762 )
...
PR Close #28762
2019-02-19 12:53:19 -08:00
47574fef11
build(bazel): temporarily pin browser versions while upstream is fixed as work-around for #28681 ( #28698 )
...
PR Close #28698
2019-02-13 19:18:27 -08:00
28bdeeef3e
build(bazel): update to rules_nodejs 0.18.6 ( #28699 )
...
PR Close #28699
2019-02-13 12:13:08 -08:00
7a6237bc50
build: update lock files ( #28532 )
...
PR Close #28532
2019-02-05 16:55:43 -05:00
57034aa13d
build: fix for integration/bazel ( #28532 )
...
PR Close #28532
2019-02-05 16:55:43 -05:00
cec1fa04c2
build: remove all deps on io_bazel_rules_go ( #28532 )
...
PR Close #28532
2019-02-05 16:55:43 -05:00
0d1e065a1c
build: update to rules_typescript 0.23.2 and rules_nodejs 0.16.8 ( #28532 )
...
PR Close #28532
2019-02-05 16:55:43 -05:00
9a965c9145
build: create dist/bin symlink with Bazel outputs ( #27781 )
...
Note that we had nasty problems in the past when this was enabled, but those have supposedly been fixed.
PR Close #27781
2019-01-22 09:52:46 -08:00
38343a2388
build: set a default module_name for ts_library rules ( #28051 )
...
PR Close #28051
2019-01-18 10:16:39 -08:00
b78351cc7e
build(bazel): Bump @bazel/typescript & @bazel/karma to 0.22.1 ( #28031 )
...
PR Close #28031
2019-01-10 16:49:56 -08:00
b47c43af45
build: bazel integration test using limited resources ( #27937 )
...
PR Close #27937
2019-01-07 15:35:10 -08:00
bf57e9d781
build: update rules_typescript ( #27586 )
...
This release of rules_typescript fixes a critical bug: typescript code
was not checked at all, including type-checking, tsetse, and strict deps
fixes #27569
PR Close #27586
2018-12-10 16:33:41 -08:00
44dd764d6d
build: update to Bazel 0.20 ( #27394 )
...
refactor Bazel RBE configs
PR Close #27394
2018-12-07 14:29:03 -08:00
15ca1bbd11
style: run latest buildifier binary ( #27489 )
...
PR Close #27489
2018-12-07 09:27:32 -08:00
c8a8dcfc6e
build(bazel): update handling of rules_nodejs transitive deps ( #27264 )
...
BREAKING CHANGES:
Bazel users: rules_angular_dependencies() will no longer install transitive dependencies of build_bazel_rules_nodejs and build_bazel_rules_typescript. User WORKSPACE files will now need to install rules_nodejs and rules_typescript transitive deps directly:
```
load("@build_bazel_rules_typescript//:package.bzl", "rules_typescript_dependencies")
rules_typescript_dependencies()
load("@build_bazel_rules_nodejs//:package.bzl", "rules_nodejs_dependencies")
rules_nodejs_dependencies()
```
PR Close #27264
2018-11-30 13:35:51 -08:00
026b7e34b3
build: update yarn version ( #27193 )
...
Some engineers were already on Yarn 0.10.x which was permitted by the range in our package.json#engines
However this introduced 'integrity sha512' lines into the yarn.lock files.
Then when engineers use yarn 0.9 (in particular, Bazel did this) then the lock files get tons of meaningless edits.
We could force everyone back to yarn 0.9 but this commit chooses to instead advance everyone past 0.10
PR Close #27193
2018-11-21 07:46:22 -08:00
81e975ad93
build: update to latest Bazel rules_typescript ( #27138 )
...
PR Close #27138
2018-11-17 12:19:32 -08:00
8fc4ae51fb
build: use bazel version from node modules ( #26691 )
...
* No longer depends on a custom CircleCI docker image that comes with Bazel pre-installed. Since Bazel is now available through NPM, we should be able to use the version from `@bazel/bazel` in order to enforce a consistent environment on CI and locally.
* This also reduces the amount of packages that need to be published (ngcontainer is removed)
PR Close #26691
2018-10-30 16:19:13 -04:00
15c2467dbd
build: review comments addressed ( #26488 )
...
PR Close #26488
2018-10-19 20:59:29 -07:00
2b3cac5b31
build: add comment to /integration/bazel/package.json ( #26488 )
...
PR Close #26488
2018-10-19 20:59:29 -07:00
8d5e3e6981
build: update to rules_typescript 0.20.3 and rules_nodejs 0.15.1 ( #26488 )
...
PR Close #26488
2018-10-19 20:59:29 -07:00
631998b2df
build: idiomatic install of @angular/bazel npm package ( #26258 ) ( #26488 )
...
PR Close #26488
2018-10-19 20:59:29 -07:00
6468711e16
build(bazel): update to rules_typescript 0.20.2 ( #26279 ) ( #26488 )
...
PR Close #26488
2018-10-19 20:59:29 -07:00
d698b0eadf
build: update to rules_typescript 0.20.1 and rules_nodejs 0.15.0 ( #26260 ) ( #26488 )
...
PR Close #26488
2018-10-19 20:59:29 -07:00
1f3331f5e6
build(bazel): use fine-grained npm deps ( #26111 ) ( #26488 )
...
PR Close #26488
2018-10-19 20:59:29 -07:00
b99d7ed5bf
build(bazel): update to rules_typescript 0.17.0 & rules_nodejs 0.13.4 ( #25920 )
...
PR Close #25920
2018-09-18 13:05:38 -07:00
bdbb2f9bfa
ci: update to bazel 0.17 ( #25967 )
...
this includes support for @ character in labels, which we need for fine-grained deps
PR Close #25967
2018-09-17 12:51:52 -07:00
34ec9244a6
build: update to Node 10 ( #25822 )
...
PR Close #25822
2018-09-06 14:58:30 -07:00
1e7a873cf4
build(bazel): remove unused angular.tsconfig.json integration/bazel test ( #25778 )
...
PR Close #25778
2018-09-05 09:38:19 -07:00
910381ddbd
build(bazel): fix bazel types reference directive resolves ( #25581 )
...
PR Close #25581
2018-08-31 11:12:03 -07:00
Greg Magolan
Matias Niemelä
Igor Minar
Alex Eagle
Wassim Chegham
Paul Gschwendtner
Keen Yee Liau
Alex Eagle