Node Error Einval Invalid Argument
Contents |
Sign in Pricing Blog Support Search GitHub This repository Watch 1,905 Star error in einval: invalid argument, uv_interface_addresses 27,975 Fork 4,635 nodejs/node Code Issues 579 Pull requests 278 nodejs windows Projects 2 Wiki Pulse Graphs New issue Bash on Windows os.networkInterfaces: EINVAL #7150 Closed neurosnap
Bash On Windows
opened this Issue Jun 4, 2016 · 4 comments Projects None yet Labels invalid os windows Milestone No milestone Assignees No
Git Bash
one assigned 4 participants neurosnap commented Jun 4, 2016 OS: Windows 10 Pro Insider Preview Build: 14352.rs1_release.160522-1930 erock@EROCK-WIN:/mnt/c/Users/Erock/$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.4 LTS Release: 14.04 Codename: trusty Node on Bash on Windows seems to fail when trying to access networkInterfaces erock@EROCK-WIN:/mnt/c/Users/Erock/$ node > var os = require('os'); undefined > os.networkInterfaces(); Error: EINVAL: invalid argument, uv_interface_addresses at Error (native) at repl:1:4 at REPLServer.defaultEval (repl.js:272:27) at bound (domain.js:280:14) at REPLServer.runBound [as eval] (domain.js:293:12) at REPLServer.
Sign in Pricing Blog Support Search GitHub This repository Watch 302 Star 2,653 Fork 91 Microsoft/BashOnWindows Code Issues 587 Pull requests 0 Projects 0 Pulse Graphs New issue os.networkInterfaces error in NodeJS / Yeoman #468 Open StfBauer opened this Issue Jun 2, 2016 · 83 comments Projects None yet Labels feature Milestone No milestone Assignees No one assigned 45 participants and others StfBauer commented Jun 2, 2016 I managed to successfully install NodeJS, NPM and Yeoman. You see all installed components in the version below. When create a new https://github.com/nodejs/node/issues/7150 project and type. yo
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more http://stackoverflow.com/questions/17297422/trouble-with-starting-node-js-from-a-cygwin-console about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users https://soyuka.me/using-nodejs-with-cygwin-v0-10-25/ Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Trouble with starting Node.js from a Cygwin console up vote 10 down vote favorite 6 I have no trouble running node.exe from a regular command prompt: C:\>node invalid argument --interactive > console.log("Works fine"); Works fine But when I try to do the same thing from a Cygwin console, I run into this: Olli@Olli-MBRr /cygdrive/c $ node.exe events.js:72 throw er; // Unhandled 'error' event ^ Error: read ENOTCONN at errnoException (net.js:900:11) at Socket._read (net.js:391:21) at Socket.Readable.read (_stream_readable.js:320:10) at Socket.read (net.js:293:43) at new Socket (net.js:185:10) at process.stdin (node.js:660:19) at startup (node.js:145:16) at node.js:901:3 At first I thought it might be because Cygwin has trouble with the path name node error einval with a space in it (C:\Program Files\nodejs), but after installing node.js to a directory with no spaces in the path name I was unable to resolve the problem. I would like to run a Node JS console from Emacs (run from Cygwin) using js-comint, but I ran into this error and have no clue how to resolve it. windows node.js emacs cygwin share|improve this question asked Jun 25 '13 at 12:31 luxbock 75125 Regarding your ending point quote(I would like to run a Node JS console from Emacs (run from Cygwin) using js-comint): (1) I have the same goal except within Emacs' M-x "shell" (I'm unfamiliar with js-comint), (2) regarding your goal -except seemingly sadly without Cygwin-, the Google Search(node emacs shell) which find 3 finds me this page I see also has as find 1 (Emacs wiki for Node.js )Using js-comint. –Destiny Architect May 11 '14 at 3:28 HEADS UP: 1.5 years before this asking, this question was essentially already asked at stackoverflow.com/questions/10043177/node-js-cygwin-not-supported; SO SEE THAT FIRST and KINDLY PUT SOLUTIONS THERE --unless they were started here first, as [Running from Cygwin.bat]( stackoverflow.com/a/23030836/2255628): then it seems best to keep the details here (since started here) and just link to them from there; there already has a number of answers not found here. –Destiny Architect May 11 '14 at 3:45 Regarding
went to the http://nodejs.org, downloaded the node-v0.10.25.msi and installed it. Back to my cygwin, I’m naturally writing: npm -v - command not found A quick google search, and I founding some strange things, they all say that nodejs and cygwin can’t work together: http://stackoverflow.com/questions/10043177/node-js-cygwin-not-supported http://stackoverflow.com/questions/17297422/trouble-with-starting-node-js-from-a-cygwin-console But I won’t let it down, and I run: /cygdrive/c/Program\ Files/nodejs/npm.cmd -v It’s working! Next step, just aliasing nodejs and npm in my bash_profile: nano ~/.bash_profile # write at the end : (or echo "" >> ~/.bash_profile) alias npm="/cygdrive/c/Program\ Files/nodejs/npm.cmd" alias node="/cygdrive/c/Program\ Files/nodejs/node.exe" # source ~/.bash_profile node -v # v0.10.25 npm -v # 1.3.24 Nodejs and cygwin aren’t working together ? Nonsense. Edit: When I tried npm useradd I had an EINVAL error : npm ERR! Error: EINVAL, invalid argument npm ERR! at new Socket (net.js:157:18) npm ERR! at process.stdin (node.js:660:19) npm ERR! at read (C:\Program Files\nodejs\node_modules\npm\node_modules\read\lib\read.js:18:36) npm ERR! at readUsername (C:\Program Files\nodejs\node_modules\npm\lib\adduser.js:40:3) npm ERR! at loop (C:\Program Files\nodejs\node_modules\npm\lib\adduser.js:33:20) npm ERR! at EventEmitter.adduser (C:\Program Files\nodejs\node_modules\npm\lib\adduser.js:29:3) npm ERR! at Object.commandCache.(anonymous function) (C:\Program Files\nodejs\node_modules\npm\lib\npm.js:194:11) npm ERR! at EventEmitter.