From 522919a537d83f612b00953b21bd83e2e2f5c4bc Mon Sep 17 00:00:00 2001
From: Igor Minar <igor@angular.io>
Date: Fri, 14 Dec 2018 07:54:22 -0800
Subject: [PATCH] fix(bazel): emit full node stack traces when Angular
 compilation crashes (#27678)

The default 10 items are often not enough to debug deeply nested compilation operations.

This PR is based on @martinprobst's http://cl/225528216.

PR Close #27678
---
 packages/bazel/src/ng_module.bzl | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/packages/bazel/src/ng_module.bzl b/packages/bazel/src/ng_module.bzl
index c429a0e978..9a4e651d40 100644
--- a/packages/bazel/src/ng_module.bzl
+++ b/packages/bazel/src/ng_module.bzl
@@ -283,6 +283,8 @@ _collect_summaries_aspect = aspect(
 _EXTRA_NODE_OPTIONS_FLAGS = [
     # Expose the v8 garbage collection API to JS.
     "--node_options=--expose-gc",
+    # Show ~full stack traces, instead of cutting off after 10 items.
+    "--node_options=--stack-trace-limit=100",
 ]
 
 def ngc_compile_action(