Change Details

``` 23:30:33 npm ERR! EEXIST, symlink '../esprima/bin/esparse.js' 23:30:33 File exists: ../esprima/bin/esparse.js 23:30:33 Move it away, and try again. ``` Caused by a bug in npm or a bug in the dev-dependencies in how they register themselves with npm. This error happens when two builds run in parallel on the same ci slave host. Upstream report: * https://github.com/npm/npm/issues/6309#issuecomment-72579930 * https://github.com/npm/npm/issues/7130#issuecomment-75508043 A recheck usually "fixes" it for now.

``` 23:30:33 npm ERR! EEXIST, symlink '../esprima/bin/esparse.js' 23:30:33 File exists: ../esprima/bin/esparse.js 23:30:33 Move it away, and try again. ``` Caused by a bug in npm or a bug in the dev-dependencies in how they register themselves with npm. This error happens when two builds run in parallel on the same ci slave host. Upstream report: * https://github.com/jscs-dev/node-jscs/issues/883 * https://github.com/npm/npm/issues/7130 A recheck usually "fixes" it for now.

``` 23:30:33 npm ERR! EEXIST, symlink '../esprima/bin/esparse.js' 23:30:33 File exists: ../esprima/bin/esparse.js 23:30:33 Move it away, and try again. ``` Caused by a bug in npm or a bug in the dev-dependencies in how they register themselves with npm. This error happens when two builds run in parallel on the same ci slave host. Upstream report: * https://github.com/npm/npm/issues/6309#jscs-dev/node-jscs/issuecomment-72579930es/883 * https://github.com/npm/npm/issues/7130#issuecomment-75508043 A recheck usually "fixes" it for now.