iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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
This commit is contained in:
Igor Minar 2018-12-14 07:54:22 -08:00 committed by Miško Hevery
parent 650c5a02ac
commit 522919a537
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
packages/bazel/src/ng_module.bzl
View File

@ -283,6 +283,8 @@ _collect_summaries_aspect = aspect(
_EXTRA_NODE_OPTIONS_FLAGS = [ _EXTRA_NODE_OPTIONS_FLAGS = [
# Expose the v8 garbage collection API to JS. # Expose the v8 garbage collection API to JS.
"--node_options=--expose-gc", "--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( def ngc_compile_action(