Long console.log cut off

[hboylan]

Trying to console.log a larger JSON object within the script I run, but the end keeps getting chopped off so I can't see the full result.

Is this supposed to happen by default?
Any workarounds to see full logs?

[spalger]

Hmmm, we pipe the output from the child process to stdout/stderr until the stdio of the child is closed [source], so that shouldn't be happening.

I wonder if node is actually getting the entire object into stdout. If you run the command directly (outside of grunt-run) do you see the entire output? What if you add a sleep after the command (you'll need to switch to the exec: style if you are using cmd: + args:)?