Fix big JSON passed from subprocess being cut short

[LarsJK]

Fixes #603

[LarsJK]

Looks like I broke async running.. Will have another go at it..

[LarsJK]

Not sure why Travis fails..

[orta]

The node 9 runner is the runner which runs Danger like a consumer CI, it looks like the JSON it thinks is the response from the subprocess is {} (logs).

Could it be that more than one JSON object is being sent over, and getting to the results processor here: https://github.com/danger/danger-js/blob/master/source/runner/Executor.ts#L122-L125

[orta]

I got a fix coming up for this in a week or two, so I'm going to close this for now 👍

[peril-staging]

Thanks for the PR @LarsJK.

The Danger org conform to the Moya Community Continuity Guidelines, which means
that we want to offer any contributor the ability to control their destiny.

So, we've sent you an org invite - thanks LarsJK 🎉

Generated by 🚫 dangerJS