Paul Gschwendtner 4f9374951d fix(bazel): ng_package cannot be run multiple times without clean (#27200) ...

Currently when building the `ng_package` multiple times, the old `ng_package` output will be copied over to the new `ng_package` content. Resulting in packages like `src/cdk/npm_package/npm_package/npm_package/AND_MORE`.

This happens because currently all TypeScript definition files are resolved from within the `binDir`. This is just wrong because it could then take up the `d.ts` files from the previous `ng_package` output. All typescript definitions that belong to the target package, should be resolved through Bazel and copied based on that computation.

Also fixes that `esm` files aren't written to the `ng_package` on Windows. This is because we try to flatten paths using the `path.delimiter` while the path is always using Posix delimiters (causing the paths to be incorrect)

PR Close #27200

2018-12-04 14:01:25 -08:00

..

docs

docs(bazel): add skydoc generation (#23544)

2018-08-08 13:12:07 -07:00

src

fix(bazel): ng_package cannot be run multiple times without clean (#27200)

2018-12-04 14:01:25 -08:00

test

fix(bazel): ng_package should correctly map to source maps in secondary entry-points (#27313)

2018-11-30 13:40:00 -08:00

BUILD.bazel

feat(bazel): ng-new schematics with Bazel (#27277)

2018-12-03 14:38:23 -08:00

check_version.js

build: idiomatic install of @angular/bazel npm package (#26258) (#26488)

2018-10-19 20:59:29 -07:00

index.bzl

build: use bazel version from node modules (#26691)

2018-10-30 16:19:13 -04:00

package.bzl

build: only stamp version info when releasing (#27362)

2018-11-30 16:08:23 -08:00

package.json

build(bazel): Add Bazel builders (#27141)

2018-11-21 07:46:42 -08:00

protractor-utils.js

build: idiomatic install of @angular/bazel npm package (#26258) (#26488)

2018-10-19 20:59:29 -07:00