Alex Eagle d1e33d2df7 build: disambiguate rollup progress message (#23318) ...

All our package labels are `npm_package` so the bazel build reports a bunch of identical actions running, like

```
    Angular Packaging: rolling up npm_package; 31s darwin-sandbox
    Angular Packaging: rolling up npm_package; 30s darwin-sandbox
    Angular Packaging: rolling up npm_package; 29s darwin-sandbox
    Angular Packaging: rolling up npm_package; 27s darwin-sandbox
    Angular Packaging: rolling up npm_package; 26s darwin-sandbox
    Angular Packaging: rolling up npm_package; 23s darwin-sandbox
    Angular Packaging: rolling up npm_package; 19s darwin-sandbox
    Angular Packaging: rolling up npm_package; 11s darwin-sandbox
```
PR Close #23318

2018-04-11 15:31:02 -07:00

..

src

build: disambiguate rollup progress message (#23318)

2018-04-11 15:31:02 -07:00

test

fix(common): workaround UMD/webpack limitation (#23271)

2018-04-09 15:16:12 -07:00

BUILD.bazel

release(bazel): change publish-next script to publish bazel artifacts (#23097)

2018-03-30 14:03:05 -07:00

index.bzl

feat(bazel): add an ng_package rule (#22221)

2018-02-23 11:19:04 -08:00

package.json

feat(bazel): change ng_package rule to APF v6 (#22782)

2018-03-15 11:38:31 -07:00