installing sync-exec using io.js

[Mark Edwards]

hello all - i just switched from node.js to io.js and ran into this problem.  i tried to run

mkdir  ./test;  cd  ./test;  npm  install sync-exec;

 and received back the following message (below)  any suggestions?

npm WARN package.json f...@0.0.2 fs is also the name of a node core module.

npm WARN package.json f...@0.0.2 No description

npm WARN package.json f...@0.0.2 No repository field.

npm WARN engine f...@1.2.5: wanted: {"node":">=0.6.0"} (current: {"node":"1.5.2-nightly201503173c8ae2d934","npm":"2.7.1"})

\

> r...@1.0.1 install /root/test/node_modules/exec-sync/node_modules/ffi/node_modules/ref

> node-gyp rebuild

gyp WARN install got an error, rolling back install

gyp ERR! configure error

gyp ERR! stack Error: 404 status code downloading tarball

gyp ERR! stack     at Request.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/install.js:246:14)

gyp ERR! stack     at emitOne (events.js:82:20)

gyp ERR! stack     at Request.emit (events.js:166:7)

gyp ERR! stack     at Request.onRequestResponse (/usr/local/lib/node_modules/npm/node_modules/request/request.js:1176:10)

gyp ERR! stack     at emitOne (events.js:77:13)

gyp ERR! stack     at ClientRequest.emit (events.js:166:7)

gyp ERR! stack     at HTTPParser.parserOnIncomingClient (_http_client.js:410:21)

gyp ERR! stack     at HTTPParser.parserOnHeadersComplete (_http_common.js:88:23)

gyp ERR! stack     at TLSSocket.socketOnData (_http_client.js:300:20)

gyp ERR! stack     at emitOne (events.js:77:13)

gyp ERR! System Linux 2.6.32-504.8.1.el6.x86_64

gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"

gyp ERR! cwd /root/stesthit/node_modules/exec-sync/node_modules/ffi/node_modules/ref

gyp ERR! node -v v1.5.2-nightly201503173c8ae2d934

gyp ERR! node-gyp -v v1.0.2

gyp ERR! not ok

npm ERR! Linux 2.6.32-504.8.1.el6.x86_64

npm ERR! argv "/usr/local/bin/iojs" "/usr/local/bin/npm" "install" "exec-sync"

npm ERR! node v1.5.2-nightly201503173c8ae2d934

npm ERR! npm  v2.7.1

npm ERR! code ELIFECYCLE

npm ERR! r...@1.0.1 install: `node-gyp rebuild`

npm ERR! Exit status 1

npm ERR!

npm ERR! Failed at the r...@1.0.1 install script 'node-gyp rebuild'.

npm ERR! This is most likely a problem with the ref package,

npm ERR! not with npm itself.

npm ERR! Tell the author that this fails on your system:

npm ERR!     node-gyp rebuild

npm ERR! You can get their info via:

npm ERR!     npm owner ls ref

npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:

npm ERR!     /root/test/npm-debug.log

[Aria Stewart]

On 2 Apr 2015, at 19:10, Mark Edwards wrote:

> hello all - i just switched from node.js to io.js and ran into this problem.  i tried to run
> mkdir  ./test;  cd  ./test;  npm  install sync-exec;
> and received back the following message (below)  any suggestions?

[snip]

> gyp ERR! stack Error: 404 status code downloading tarball

node-gyp is downloading node's source to get the headers for the version you're using. That's not being found

> gyp ERR! node -v v1.5.2-nightly201503173c8ae2d934
> gyp ERR! node-gyp -v v1.0.2

Because you're using an extremely particular version that was never meant to have a long lifetime.

Install iojs 1.6.3, perhaps?

Aria

[Ryan Schmidt]

On Apr 2, 2015, at 6:10 PM, Mark Edwards wrote:
>
> hello all - i just switched from node.js to io.js and ran into this problem. i tried to run
>
> mkdir ./test; cd ./test; npm install sync-exec;
>
> and received back the following message (below) any suggestions?

A synchronous version of exec is included in node 0.12, and I imagine in iojs as well:

https://nodejs.org/api/child_process.html#child_process_child_process_execsync_command_options

So you should use that instead of sync-exec or exec-sync or any of a number of other prior implementations found in npm.