You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using npm-run-all for scripts that build SCSS and JS (transpiling, bundling, compressing, ...). This works quite well, but when I try to execute these scripts in parallel, I occasionally run into errors.
Sometimes it works, so maybe it's even related to the performance of the machine, etc.
It doesn't make a different if I use npm or yarn; same behavior.
Can piping and/or redirection be a problem, when executing in parallel? Did I miss a limitation?
I would be grateful of for any hint 😃
The text was updated successfully, but these errors were encountered:
I apology that I have overlooked the notification of this issue.
Thank you for the report.
Interesting. I have not been aware of the limitation about this issue. The error message "Error: EAGAIN: resource temporarily unavailable, write\n✖ Processing stdin" indicates there is the problem around the piping in the script`. I need to investigate more.
I'm getting this as well but I'm not using npm-run-all, I think the issue might lie with node-sass but I'm not sure what exactly is throwing the error.
I'm using
npm-run-all
for scripts that build SCSS and JS (transpiling, bundling, compressing, ...). This works quite well, but when I try to execute these scripts in parallel, I occasionally run into errors.I stripped it down and put it in a repository: https://github.com/nesmyslny/npm-script-issue
These are the scripts in
package.json
:Executing them sequentially works (
npm run build-s
). But in parallel (npm run build-p
) I get, for example, that output:Sometimes it works, so maybe it's even related to the performance of the machine, etc.
It doesn't make a different if I use
npm
oryarn
; same behavior.Can piping and/or redirection be a problem, when executing in parallel? Did I miss a limitation?
I would be grateful of for any hint 😃
The text was updated successfully, but these errors were encountered: