Builds have started failing due to the following error
make: Entering directory
/home/ubuntu/SCiCustomer/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws/build' CXX(target) Release/obj.target/bufferutil/src/bufferutil.o SOLINK_MODULE(target) Release/obj.target/bufferutil.node COPY Release/bufferutil.node CXX(target) Release/obj.target/validation/src/validation.o SOLINK_MODULE(target) Release/obj.target/validation.node COPY Release/validation.node make: Leaving directory
/home/ubuntu/SCiCustomer/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws/build’
npm ERR! fetch failed https ://registry.npmjs.org/i/-/i-0.3.2.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 504
npm ERR! fetch failed https ://registry.npmjs.org/i/-/i-0.3.2.tgz.
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 504
npm ERR! fetch failed https ://registry.npmjs.org/i/-/i-0.3.2.tgz
npm ERR! Linux 3.13.0-79-generic
npm ERR! argv “node” “/home/ubuntu/nvm/v0.10.33/bin/npm” “install”
npm ERR! node v0.10.33
npm ERR! npm v2.13.5
npm ERR! code ECONNRESET
npm ERR! network socket hang up
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network ‘proxy’ config is set properly. See: ‘npm help config’
npm ERR! Please include the following file with any support request:
npm ERR! /home/ubuntu/SCiCustomer/npm-debug.log
npm install returned exit code 1
npm install returned exit code 1