one query is supported "some_path", which gives you a way to determine how a
function is included in the program. For example, running:
dart code_deps.dart angular2_hello.js.info.json some_path main Compiler
would produce this output:
source: examples.src.hello_world.index...main
target: angular2.src.core.compiler.compiler...Compiler.Compiler
result:
0. examples.src.hello_world.index...main
1. examples.src.gestures.index.ng_deps.dart...initReflector
2. angular2.bootstrap_static.ng_deps.dart...initReflector
3. angular2.application_static.ng_deps.dart...initReflector
4. angular2.src.core.application_common.ng_deps.dart...initReflector
5. angular2.src.core.compiler.compiler.ng_deps.dart...initReflector
6. angular2.src.core.compiler.compiler...Compiler.Compiler
The tool accepts regular expressions to match the name of the elements.
The graph and util library will be used for other scripts as well.
R=het@google.com
Review URL: https://codereview.chromium.org//1284843002 .
libraries.
For example, running this on the dump-info of angular2 'hello
world' would produce:
path 8807 1.21%
stack_trace 11501 1.59%
intl 14135 1.95%
Loose files 142311 19.62%
angular2 224171 30.90%
Core libs 225120 31.03%
All packages 258614 35.65%
TOTAL 626045 86.30%
Note that the grouping of libraries, say by package, and summary information is
configurable.
R=het@google.com
Review URL: https://codereview.chromium.org//1287543002 .
