-
-
Notifications
You must be signed in to change notification settings - Fork 321
Description
Describe the bug
lerna stdout maxBuffer exceeded
Error Log
nodejs-starter-kit | lerna ERR! MaxBufferError: stdout maxBuffer exceeded
nodejs-starter-kit | lerna ERR! at PassThrough.stream.on (/usr/src/app/node_modules/get-stream/index.js:41:19)
nodejs-starter-kit | lerna ERR! at PassThrough.emit (events.js:194:15)
nodejs-starter-kit | lerna ERR! at addChunk (_stream_readable.js:284:12)
nodejs-starter-kit | lerna ERR! at readableAddChunk (_stream_readable.js:261:13)
nodejs-starter-kit | lerna ERR! at PassThrough.Readable.push (_stream_readable.js:220:10)
nodejs-starter-kit | lerna ERR! at PassThrough.Transform.push (_stream_transform.js:151:32)
nodejs-starter-kit | lerna ERR! at PassThrough.afterTransform (_stream_transform.js:92:10)
nodejs-starter-kit | lerna ERR! at PassThrough._transform (_stream_passthrough.js:42:3)
nodejs-starter-kit | lerna ERR! at PassThrough.Transform._read (_stream_transform.js:190:10)
nodejs-starter-kit | lerna WARN complete Waiting for 1 child process to exit. CTRL-C to exit immediately.
nodejs-starter-kit | lerna ERR! lerna stdout maxBuffer exceeded
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Desktop :
All devices, ps I don't think browser matters in this situation
Additional context
I have a complex page that quries different kinds of data from backend buf after the app runs for a while, the above error shows up, I read related issues on lerna repo, most of them point to upgrading lerna or its dependency execa but they don't seem to solve the problem. It even persists after passing max-buffer=[some large memory] after yarn watch in package.json.
Is There a way to increase stdout and stderr maxBuffer sizes for the lerna run operations for yarn watch and yarn build?
@larixer any help would be appreciated.
Thank you for your help!