Wanted to request some directions/examples on how to use broccoli-viz in the README.

Also thanks for all the awesome work @stefanpenner !

right now they are hard coded, but we could use Maths/Stats to improve this further.

http://static.iamstef.net/basic-ordered-cli-app.png

Is it possible to just output a dependency tree? I'm unsure if that would be in scope for this module. I'd be happy to take a stab at implementing.

Hi,

After installing broccoli viz globally is there some configuration needed as I am getting following when I run BROCCOLI_VIZ=1 ember build

BROCCOLI_VIZ=1 : The term 'BROCCOLI_VIZ=1' is not recognized as the name of a cmdlet,

Currently its kinda ghetto (but helps already)

We should likely ensure the edges look appropriate relative to the cost introduced into the larger graph

current UI: http://static.iamstef.net/basic-ordered-cli-app.png

This will allow us to deprecate the nodes output in writeVizInfo in ember-cli so that the on-disk format can be the same as what the hook receives.

see ember-cli/ember-cli#6546

cc @rwjblue @stefanpenner

... to make GreenKeeper more happier 😉

context: ember-cli/broccoli-builder#7

• display node.id.broccoliId instead of node._id (or maybe in addition to)
• display truthy node.id.broccoliCachedNode differently from falsy

After doing:

BROCCOLI_VIZ=1 SITE=sitename ember build I get a number of instrumentation files:
https://www.dropbox.com/s/df4zovvqhbyfygj/instrumentation.zip?dl=0

When I run:
broccoli-viz instrumentation.build.0.json > instrumentation.build.0.dot

It crashes:

/usr/local/Cellar/node@6/6.14.1/lib/node_modules/broccoli-viz/lib/build-graph.js:23
  node.children.forEach(function (id) {
      ^

TypeError: Cannot read property 'children' of undefined
    at visitPostOrder (/usr/local/Cellar/node@6/6.14.1/lib/node_modules/broccoli-viz/lib/build-graph.js:23:7)
    at /usr/local/Cellar/node@6/6.14.1/lib/node_modules/broccoli-viz/lib/build-graph.js:25:5
    at Array.forEach (native)
    at visitPostOrder (/usr/local/Cellar/node@6/6.14.1/lib/node_modules/broccoli-viz/lib/build-graph.js:23:17)
    at annotateNodes (/usr/local/Cellar/node@6/6.14.1/lib/node_modules/broccoli-viz/lib/build-graph.js:32:3)
    at module.exports (/usr/local/Cellar/node@6/6.14.1/lib/node_modules/broccoli-viz/lib/build-graph.js:79:10)
    at Object.processNodes [as process] (/usr/local/Cellar/node@6/6.14.1/lib/node_modules/broccoli-viz/lib/process.js:5:15)
    at Object.<anonymous> (/usr/local/Cellar/node@6/6.14.1/lib/node_modules/broccoli-viz/bin/broccoli-viz:35:25)
    at Module._compile (module.js:577:32)
    at Object.Module._extensions..js (module.js:586:10)

http://www.graphviz.org/Documentation/dotguide.pdf

Is there a way to filter out nodes that report 0ms?

I'd like to get to the bottom of our build time issues and broccoli-viz is incredibly helpful. However the output is cluttered with hundreds of 0ms nodes that aren't contributing to the problem. They're mostly Addon#treeFor. Is there a straightforward way to remove those without affecting the integrity of the visualization?