build: allow bazel build ...

.circleci/config.yml

@@ -62,7 +62,7 @@ jobs:
       # Use bazel query so that we explicitly ask for all buildable targets to be built as well
       # This avoids waiting for a build command to finish before running the first test
       # See https://github.com/bazelbuild/bazel/issues/4257
-      - run: bazel query --output=label '//modules/... union //packages/... union //tools/...' | xargs bazel test --config=ci
+      - run: bazel query --output=label //... | xargs bazel test --config=ci
 
       # CircleCI will allow us to go back and view/download these artifacts from past builds.
       # Also we can use a service like https://buildsize.org/ to automatically track binary size of these artifacts.

WORKSPACE

@@ -28,6 +28,11 @@ local_repository(
     path = "node_modules/rxjs/src",
 )
 
+local_repository(
+    name = "bazel_integration_test",
+    path = "integration/bazel",
+)
+
 git_repository(
     name = "com_github_bazelbuild_buildtools",
     remote = "https://github.com/bazelbuild/buildtools.git",

package.json

@@ -63,7 +63,6 @@
     "cors": "2.8.4",
     "domino": "1.0.29",
     "entities": "1.1.1",
-    "firebase-tools": "3.12.0",
     "firefox-profile": "1.0.3",
     "fs-extra": "4.0.2",
     "glob": "7.1.2",
@@ -86,6 +85,7 @@
     "madge": "0.5.0",
     "minimist": "1.2.0",
     "node-uuid": "1.4.8",
+    "protobufjs": "5.0.0",
     "protractor": "5.1.2",
     "rewire": "2.5.2",
     "rollup": "0.47.4",