############################### # Typescript / Angular / Sass # ############################### # Make compilation fast, by keeping a few copies of the compilers # running as daemons, and cache SourceFile AST's to reduce parse time. build --strategy=TypeScriptCompile=worker build --strategy=AngularTemplateCompile=worker # Enable debugging tests with --config=debug test:debug --test_arg=--node_options=--inspect-brk --test_output=streamed --test_strategy=exclusive --test_timeout=9999 --nocache_test_results ############################### # Filesystem interactions # ############################### # Don't create symlinks like bazel-out in the project. # These cause VSCode to traverse a massive tree, opening file handles and # eventually a surprising failure with auto-discovery of the C++ toolchain in # MacOS High Sierra. # See https://github.com/bazelbuild/bazel/issues/4603 build --symlink_prefix=/ # Performance: avoid stat'ing input files build --watchfs # Turn off legacy external runfiles run --nolegacy_external_runfiles test --nolegacy_external_runfiles ############################### # Release support # ############################### # Releases should always be stamped with version control info build --workspace_status_command=./tools/bazel_stamp_vars.sh ############################### # Output # ############################### # A more useful default output mode for bazel query # Prints eg. "ng_module rule //foo:bar" rather than just "//foo:bar" query --output=label_kind # By default, failing tests don't print any output, it goes to the log file test --test_output=errors # Show which actions are run under workers, # and print all the actions running in parallel. # Helps to demonstrate that bazel uses all the cores on the machine. build --experimental_ui test --experimental_ui ################################ # Settings for CircleCI # ################################ # Bazel flags for CircleCI are in /.circleci/bazel.rc ################################ # Temporary Settings for Ivy # ################################ # to determine if the compiler used should be Ivy or ViewEngine one can use `--define=compile=aot` on # any bazel target. This is a temporary flag until codebase is permanently switched to Ivy. build --define=compile=legacy