stdout maxBuffer exceeded when run on large projects

[JamieMason]

When running on a large git log, the following happens.

Error: stdout maxBuffer exceeded.
    at Socket.<anonymous> (child_process.js:244:12)
    at emitOne (events.js:77:13)
    at Socket.emit (events.js:169:7)
    at readableAddChunk (_stream_readable.js:146:16)
    at Socket.Readable.push (_stream_readable.js:110:10)
    at Pipe.onread (net.js:523:20)

A quick fix can be found by changing index.js:89 from

exec(command, function(err, stdout, stderr) {

to

exec(command, { maxBuffer: Infinity }, function(err, stdout, stderr) {

or by using child_process.spawn instead.

Hope this helps, thanks!

[domharrington]

Thanks for reporting. This has already been raised here: #16. Happy to accept a pull request with either approach!

[domharrington]

This can now be done via the execOptions option: https://github.com/domharrington/node-gitlog#execoptions