stdout maxBuffer exceeded

[pixeldrew]

{ Error: stdout maxBuffer exceeded
at Socket.onChildStdout (child_process.js:258:14)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at readableAddChunk (_stream_readable.js:178:18)
at Socket.Readable.push (_stream_readable.js:136:10)
at Pipe.onread (net.js:561:20) cmd: 'npm publish --tag snapshot' }

npm version
{ npm: '5.7.1',
ares: '1.10.1-DEV',
cldr: '30.0.3',
http_parser: '2.7.0',
icu: '58.2',
modules: '51',
node: '7.10.1',
openssl: '1.0.2k',
tz: '2016j',
unicode: '9.0',
uv: '1.11.0',
v8: '5.5.372.43',
zlib: '1.2.11' }

Also, it'd be good to have the output of npm publish given as a log to stdout.

[pixeldrew]

Suggest having an option to override the exec's default stdout maxBuffer Limit and redirect the publish commands to process.stdout/stderr

[keirlawson]

Thanks for the bug report :) Are you able to share a snippet of code demonstrating the issue? or the output when you run an npm publish manually? I think having an option to override the buffer size is probably a good idea, but keen to see an example of what's causing the issue first.

[pixeldrew]

Can't share the output of our build log since it's a paid project, but can tell you the things the package does whilst building. As a part of prepare: Copies files Babel compiles to es5 Runs webpack to bundle css/js dependencies this includes postcss+plugins logging Another webpack build for SSR As a part of prepublishonly: npm test (which tests over 150 components) as a final sanity before publishing. The log for all of this ends up being quite large and crashed your app. I ended up writing another tool that combines the versioning to snapshot then snapshot deployments.

[pixeldrew]

If I get some time I'll submit a pr

[keirlawson]

Ok great, a PR would be fantastic. In the mean time I have increased the default buffer by 10x on master to make this issue less likely, but an option to set the buffer size and to display stdout would both be great additions