angular-cn/packages/bazel
Keen Yee Liau 85866defa4 fix(bazel): Set module_name and enable ng test (#27715)
Relative imports in Typescript files only work when module_name is
defined in ts_library (when run in Node.js).
See issue https://github.com/bazelbuild/rules_typescript/issues/360

With that fixed, `ng test` now works.

`ng build` requires `node_modules` to be available in the project
directory, so it's not usable yet. Running `yarn` in project directory
does not work because of postinstall version check.

PR Close #27715
2018-12-17 16:43:09 -08:00
..
docs docs(bazel): add skydoc generation (#23544) 2018-08-08 13:12:07 -07:00
src fix(bazel): Set module_name and enable ng test (#27715) 2018-12-17 16:43:09 -08:00
test fix(ivy): enable flat module index production in Bazel (#27655) 2018-12-13 14:55:15 -08:00
BUILD.bazel build: restrict visibility of npm_package targets (#27611) 2018-12-14 10:20:40 -08:00
check_version.js fix(bazel): fix major/minor semver check between @angular/bazel npm packager version and angular bazel repo version (#27635) 2018-12-13 10:59:14 -08:00
index.bzl build: use bazel version from node modules (#26691) 2018-10-30 16:19:13 -04:00
package.bzl build: update rules_typescript (#27586) 2018-12-10 16:33:41 -08:00
package.json fix(bazel): Read latest versions from latest-versions.ts & use semver check (#27526) 2018-12-10 16:35:42 -08:00
protractor-utils.js build: idiomatic install of @angular/bazel npm package (#26258) (#26488) 2018-10-19 20:59:29 -07:00
yarn.lock fix(bazel): Read latest versions from latest-versions.ts & use semver check (#27526) 2018-12-10 16:35:42 -08:00