
Utilize the Closure compiler in Bazel to transpile. As part of this, a rather large file of 'externs' must be added in order to call external code. This file is specific to Polymer and copied from the Closure Github, and should be synced any time there are major changes to Polymer. Test Plan: - run `bazel build polygerrit` and verify that whitespaces are removed from resulting gr-app.js file - run `bazel build Documentation:licenses.txt` and verify that the new dependency is listed in resulting bazel-genfiles/Documentation/licenses.txt TODO in later changes: - Get closure optimizations working - Explore sourcemaps possibilities - Maybe use closure linting? Change-Id: Ic358743dda7286fea3ac1e95a7991a92c96d6341 (cherry picked from commit 1ea918bd367c091fb4128ab33d8ca7c61cfe770c)
3 lines
111 B
Plaintext
3 lines
111 B
Plaintext
build --workspace_status_command=./tools/workspace-status.sh --strategy=Closure=worker
|
|
test --build_tests_only
|