History

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

bazel-workspace

fix(bazel): Set module_name and enable ng test (#27715 )

2018-12-17 16:43:09 -08:00

ng-new

test(bazel): integration test for ng new with Bazel (#27659 )

2018-12-14 10:19:22 -08:00

BUILD.bazel

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

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

collection.json

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

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

README.md

feat(bazel): Bazel workspace schematics (#26971 )

2018-11-16 12:18:06 -08:00

README.md

Schematics for Bazel

Development notes

To test any local changes, run

bazel build //packages/bazel:npm_package

then cd to the npm package in the dist folder and run yarn link. Next run yarn link again in the directory where the ng command is invoked. Make sure the ng command is local, and not the global installation.

Generate .d.ts file from JSON schema

The script to generate .d.ts file is located in the Angular CLI repo. Make sure the CLI repository is checked out on your local machine.

Then, in the CLI repository, run the following command

bazel run //tools:quicktype_runner -- \
  ~/Documents/GitHub/angular/packages/bazel/src/schematics/ng-new/schema.json \
  ~/Documents/GitHub/angular/packages/bazel/src/schematics/ng-new/schema.d.ts

TODOs

Make the ts_json_schema rule re-usable and portable.
Add comments in BUILD files. See discussion here.