Skip to content
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.

0.11.14 on Windows ... "child_process: customFds option is deprecated" error #8492

Closed
stevenvachon opened this issue Oct 2, 2014 · 5 comments

Comments

@stevenvachon
Copy link

I'm not using customFds anywhere in my code:

// util.js
function shell(shellfile, args, callback) {
    args = ["./"+shellfile].concat(args);
    child_process.execFile("node", args, {cwd:__dirname}, callback);
}

// cli.js
util.shell("meta/app", ["--input","folder/file.ext", "--output","folder/file.ext"], function(error, stdout, stderr) {
    // mocha+chai stuff
});

yet, I get this error when running Node v0.11.14:

npm : child_process: customFds option is deprecated, use stdio instead.
At line:1 char:1
 npm test # PowerShell

npm test is in my package.json

  • This did not occur on Windows with v0.11.13
  • This did not occur on Linux with v0.11.13 nor v0.11.14 (log)
  • This only occurs on Windows with v0.11.14 (log)
  • This kills my mocha test
@stevenvachon stevenvachon changed the title 0.11.14 ... "child_process: customFds option is deprecated" error 0.11.14 on Windows ... "child_process: customFds option is deprecated" error Oct 2, 2014
@cjihrig
Copy link

cjihrig commented Oct 2, 2014

This is only a deprecation message. The feature was deprecated in this commit. Even though your code isn't using it, it appears to be used in npm and mocha.

@stevenvachon
Copy link
Author

But if it's just a warning, why does it make my mocha tests fail?

@chrisdickinson
Copy link

The deprecation notice is merely advisory output, and does not otherwise affect the flow of your program.

It might be a red herring -- there may be another issue that's causing the tests to fail. Alternatively, if your mocha tests are testing output (somehow) they might be getting the deprecation notice unexpectedly and failing.

@othiym23
Copy link

othiym23 commented Oct 2, 2014

As npm has dropped compatibility with Node 0.6, I'll be going through its code base and cleaning up its usage of customFds; it's worth pointing out that node-gyp also uses it, (as does CoffeeScript and promzard and probably many other things). Is the schedule to remove it by 1.0? Or (assuming there is one) 0.14?

othiym23 added a commit to npm/npm that referenced this issue Oct 2, 2014
Will break "explore" and "help" under Node 0.6, but npm 2 no longer
supports Node 0.6, so it's OK. Partially addresses nodejs/node-v0.x-archive#8492.
@monolithed
Copy link

> fsevents@0.3.1 install /usr/local/www/node_modules/grunt-polyfill-service/node_modules/polyfill-service/node_modules/6to5/node_modules/chokidar/node_modules/fsevents
> node-gyp rebuild

child_process: customFds option is deprecated, use stdio instead.
  SOLINK_MODULE(target) Release/.node
  SOLINK_MODULE(target) Release/.node: Finished
  CXX(target) Release/obj.target/fse/fsevents.o
  SOLINK_MODULE(target) Release/fse.node
  SOLINK_MODULE(target) Release/fse.node: Finished
npm ERR! Failed resolving git HEAD (https://github.com/matthew-andrews/fetch) fatal: bad object 9fe698067f2667f0dcc9aca6e56fcd14274143cf
npm ERR! Failed resolving git HEAD (https://github.com/matthew-andrews/fetch) 
npm ERR! Darwin 14.1.0
npm ERR! argv "node" "/usr/local/bin/npm" "install"
npm ERR! node v0.12.0
npm ERR! npm  v2.5.1
npm ERR! code 128

npm ERR! Command failed: git rev-list -n1 9fe698067f2667f0dcc9aca6e56fcd14274143cf
npm ERR! fatal: bad object 9fe698067f2667f0dcc9aca6e56fcd14274143cf
npm ERR! 
npm ERR! 
npm ERR! If you need help, you may report this error at:
npm ERR!     <http://github.com/npm/npm/issues>

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

I don't know who uses customFds but I am really not happy

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants