angular-cn/tools/symbol-extractor
Paul Gschwendtner dd59b1d371 build: unable to accept new symbol-extractor golden on windows (#30127)
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 #30127
2019-04-26 16:35:51 -07:00
..
symbol_extractor_spec test: improve symbol-extractor test by ignoring $1 suffix (#28098) 2019-01-14 09:55:30 -08:00
BUILD.bazel build: rules_nodejs 0.26.0 & use @npm instead of @ngdeps now that downstream angular build uses angular bundles (#28871) 2019-02-28 12:06:36 -08:00
cli.ts build: unable to accept new symbol-extractor golden on windows (#30127) 2019-04-26 16:35:51 -07:00
index.bzl build: unable to accept new symbol-extractor golden on windows (#30127) 2019-04-26 16:35:51 -07:00
symbol_extractor.ts ci: fix symbol test to handle duplicate symbols (#28459) 2019-01-31 12:26:16 -05:00
symbol_extractor_spec.ts