18 Commits

Author SHA1 Message Date
Joey Perrott
b8b8535f40 build: update tools directory for latest changes in rules_nodejs ()
Update the scripts/tooling in the tools directory to handle the changes in the latest
version of rules_nodejs.

PR Close 
2021-02-09 10:48:43 -08:00
Joey Perrott
284c70ee9d build: add tag to symbol-extractor tests ()
Add a tag to symbol-extractor tests to allow for bazel querying.

PR Close 
2020-09-14 16:54:36 -07:00
Joey Perrott
d1ea1f4c7f build: update license headers to reference Google LLC ()
Update the license headers throughout the repository to reference Google LLC
rather than Google Inc, for the required license headers.

PR Close 
2020-05-26 14:26:58 -04:00
Greg Magolan
63fbc71439 build: don't use deprecated $(location) pre-declared variable ()
$(location) is not recommended in the bazel docs as depending on context it will either return the value of $(execpath) or $(rootpath). rules_nodejs now supports $(rootpath) and $(execpath) in templated_args of nodejs_binary.

PR Close 
2020-03-31 11:02:56 -07:00
Joey Perrott
4022376b3f build: update scripting and tooling to rely on define=angular_ivy_enabled instream of define=compile ()
We need to migrate to using angular_ivy_enabled value to determine whether to use
Ivy or ViewEngine for package building scripts and for size-tracking and
symbol-extract tooling.

PR Close 
2019-11-26 16:38:40 -05:00
Greg Magolan
4ee354da99 build: switch to @build_bazel_rules_nodejs//:index.bzl load point ()
The defs.bzl load point will be removed for the rules_nodejs 1.0 release.

PR Close 
2019-10-28 10:10:48 -07:00
Alex Eagle
ef0b2cc74d build: convert entry_point to label ()
PR Close 
2019-06-11 00:03:11 +00:00
Paul Gschwendtner
dd59b1d371 build: unable to accept new symbol-extractor golden on windows ()
Currently when working on Windows, it's not possible to accept a new
golden for a `symbol-extractor` Bazel test. This is because the generated
executable output from the `nodejs_binary` rule (without a macro) misses
a Windows executable wrapper that sets up the proper environment
variables for the runfiles. Causing the following failure on Windows:

```
 >>>> FAIL: RUNFILES environment variable is not set. <<<<
```

PR Close 
2019-04-26 16:35:51 -07:00
Greg Magolan
ea09430039 build: rules_nodejs 0.26.0 & use @npm instead of @ngdeps now that downstream angular build uses angular bundles ()
PR Close 
2019-02-28 12:06:36 -08:00
Igor Minar
4b51d31aea build: fix symbol-extractor by passing through "compile" as environmental variable ()
PR Close 
2018-10-26 14:48:05 -04:00
Greg Magolan
15c2467dbd build: review comments addressed ()
PR Close 
2018-10-19 20:59:29 -07:00
Greg Magolan
1f3331f5e6 build(bazel): use fine-grained npm deps () ()
PR Close 
2018-10-19 20:59:29 -07:00
Greg Magolan
b99d7ed5bf build(bazel): update to rules_typescript 0.17.0 & rules_nodejs 0.13.4 ()
PR Close 
2018-09-18 13:05:38 -07:00
Greg Magolan
9605456b66 build: refactor ambient node & jasmine types so they are only included where needed ()
PR Close 
2018-08-16 13:46:43 -07:00
Alex Eagle
a3f1e2cb42 style: format .bzl files with buildifier ()
PR Close 
2018-08-08 13:12:07 -07:00
Greg Magolan
1e74ea9e60 build(bazel): update to rule_nodejs 0.10.0 ()
PR Close 
2018-07-06 10:17:36 -07:00
Miško Hevery
bfe35dac85 fix(ivy): change symbol-extractor to use .accept rather than -—define UPDATE_GOLDEN=1 ()
Using `-—define` causes bazel to bust the cache which means that doing
`bazel test target` followed by `bazel run -—define UPDATE_GOLDEN=1 target` will
cause caches to be invalidated and house full rebuild.

PR Close 
2018-03-22 18:02:48 -04:00
Miško Hevery
20a900b648 test: Add bundle symbol extractor tool ()
This tool will be used for extracting symbols out of bundles so that
we can assert that only whitelisted symbols are allowed.

PR Close 
2018-02-13 11:28:54 -08:00