New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase the stdout/stderr buffer for npm install #3887

Closed
wants to merge 1 commit into
base: devel
from

Conversation

Projects
None yet
2 participants
@mitar
Collaborator

mitar commented Mar 9, 2015

Otherwise for some npm packages which output a lot during install, installation simply fails with no clear error message. node.js kills the process and there is no information about that in anything Meteor prints out: "maxBuffer specifies the largest amount of data allowed on stdout or stderr - if this value is exceeded then the child process is killed."

Increase the stdout/stderr buffer for npm install.
Otherwise for some npm packages which output a lot during install, installation simply fails with no clear error message. node.js kills the process and there is no information about that in anything Meteor prints out: "maxBuffer specifies the largest amount of data allowed on stdout or stderr - if this value is exceeded then the child process is killed."
@glasser

This comment has been minimized.

Member

glasser commented Mar 10, 2015

Good catch. Do you have an example of a module which doesn't work without this and does work with it?

@glasser

This comment has been minimized.

Member

glasser commented Mar 10, 2015

(In any case, merged, thanks!)

@glasser glasser closed this Mar 10, 2015

@mitar

This comment has been minimized.

Collaborator

mitar commented Mar 10, 2015

I have my own module: https://github.com/peerlibrary/node-meteor-package-builder :-) It installs Meteor dev bundle during module installation and because you use curl with -# switch there is a lot of output. Maybe also one solution would be that -# in curl in meteor bootstrap script would be able to be silenced with an env variable.

@mitar mitar deleted the mitar:patch-11 branch Mar 10, 2015

@mitar

This comment has been minimized.

Collaborator

mitar commented Mar 10, 2015

(At the moment I simply modified the node package to send the output to dev null when installing, but that might hide potential issues.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment