... Just need some more reading ...

  # TODO(): Figure out 
  # push:
  #   branches:
  #     - master
  # pull_request: {}

When yarn|npm flattening, multiple packages will resolve to single installed locations in findProdInstalls, which means we're traversing and finding the same thing multiple times.

• Cache found locations of packages.
• Check cache before doing actual disk I/O
• Make sure we're doing things correctly concurrency-wise.

• Infer if production dependency package.json
• Keep glob
• Add tests

• Check forms of bin
• Fix and add tests.

Like in lerna / yarn workspaces projects.

See FormidableLabs/trace-pkg#39

If a dependency cannot be found it is currently silently ignored.

• Decide on approach to missing installs. (Different return structure? Function handler?)
• Decide on shape of object to return on missing installs. (Parent dependency? Name?)