gatsby: ERR_IPC_CHANNEL_CLOSED on gatsby build

Description

I keep running into this error when trying to gatsby build:

Unhandled rejection Error [ERR_IPC_CHANNEL_CLOSED]: channel closed
    at process.target.send (internal/child_process.js:578:16)
    at reportSuccess (/Users/sacha/Dev/StateOfJS/surveys/2018/website/node_modules/jest-worker/build/child.js:59:11)
    at tryCatcher (/Users/sacha/Dev/StateOfJS/surveys/2018/website/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/Users/sacha/Dev/StateOfJS/surveys/2018/website/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/Users/sacha/Dev/StateOfJS/surveys/2018/website/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromise0 (/Users/sacha/Dev/StateOfJS/surveys/2018/website/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/Users/sacha/Dev/StateOfJS/surveys/2018/website/node_modules/bluebird/js/release/promise.js:694:18)
    at Promise._fulfill (/Users/sacha/Dev/StateOfJS/surveys/2018/website/node_modules/bluebird/js/release/promise.js:638:18)
    at MappingPromiseArray.PromiseArray._resolve (/Users/sacha/Dev/StateOfJS/surveys/2018/website/node_modules/bluebird/js/release/promise_array.js:126:19)
    at MappingPromiseArray._promiseFulfilled (/Users/sacha/Dev/StateOfJS/surveys/2018/website/node_modules/bluebird/js/release/map.js:101:18)
    at Promise._settlePromise (/Users/sacha/Dev/StateOfJS/surveys/2018/website/node_modules/bluebird/js/release/promise.js:574:26)
    at Promise._settlePromise0 (/Users/sacha/Dev/StateOfJS/surveys/2018/website/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/Users/sacha/Dev/StateOfJS/surveys/2018/website/node_modules/bluebird/js/release/promise.js:694:18)
    at _drainQueueStep (/Users/sacha/Dev/StateOfJS/surveys/2018/website/node_modules/bluebird/js/release/async.js:138:12)
    at _drainQueue (/Users/sacha/Dev/StateOfJS/surveys/2018/website/node_modules/bluebird/js/release/async.js:131:9)
    at Async._drainQueues (/Users/sacha/Dev/StateOfJS/surveys/2018/website/node_modules/bluebird/js/release/async.js:147:5)

Any idea what’s going on?

Environment


  System:
    OS: macOS High Sierra 10.13.6
    CPU: x64 Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 8.12.0 - ~/.nvm/versions/node/v8.12.0/bin/node
    Yarn: 1.7.0 - /usr/local/bin/yarn
    npm: 6.4.1 - ~/.nvm/versions/node/v8.12.0/bin/npm
  Browsers:
    Chrome: 69.0.3497.100
    Firefox: 61.0.2
    Safari: 12.0
  npmPackages:
    gatsby: 2.0.18 => 2.0.18 
    gatsby-link: ^2.0.4 => 2.0.4 
    gatsby-plugin-google-analytics: ^2.0.6 => 2.0.6 
    gatsby-plugin-netlify: ^2.0.1 => 2.0.1 
    gatsby-plugin-react-helmet: ^3.0.0 => 3.0.0 
    gatsby-plugin-sass: ^2.0.1 => 2.0.1 
    gatsby-source-filesystem: ^2.0.1 => 2.0.1 
    gatsby-transformer-yaml: ^2.1.3 => 2.1.3 
  npmGlobalPackages:
    gatsby-cli: 2.4.2

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 16 (5 by maintainers)

Most upvoted comments

I’m also experiencing this issue, without any console.logs in my code

snackersteph on Aug 29, 2019

I can confirm in my project, a component doing console.log was causing the build to fail.

zivc on Oct 22, 2018

This went away eventually. I noticed it tended to happen more when I was using console.logs to debug my code, so I wonder if it might be caused by the build process outputting too many logs somehow? Although it might also be a coincidence.

SachaG on Oct 13, 2018

@kpennell Sorry: that was like 15 errors ago. At this point I’m not sure what fixed this particular error.

rafael-nogueras on Nov 13, 2019