WSL: Node: invalid argument, uv_interface_addresses

Node 7.0 Windows build 14965.1001

Create test.js:

var os = require("os");
os.networkInterfaces();
node ./test.js

Output:

os.networkInterfaces();                                 
   ^                                                    
                                                        
Error: EINVAL: invalid argument, uv_interface_addresses 
    at Object.<anonymous> (/home/asvetl/test.js:3:4)    
    at Module._compile (module.js:573:32)               
    at Object.Module._extensions..js (module.js:582:10) 
    at Module.load (module.js:490:32)                   
    at tryModuleLoad (module.js:449:12)                 
    at Function.Module._load (module.js:441:3)          
    at Module.runMain (module.js:607:10)                
    at run (bootstrap_node.js:382:7)                    
    at startup (bootstrap_node.js:137:9)                
    at bootstrap_node.js:497:3

In my case i was trying to run webpack with css-loader (the error comes from it).

About this issue

  • Original URL
  • State: closed
  • Created 10 years ago
  • Reactions: 6
  • Comments: 20 (5 by maintainers)

Most upvoted comments

I already had this issue and I’m doing this as a workaround:

// hack for Ubuntu on Windows
try {
  require('os').networkInterfaces();
}
catch (e) {
  require('os').networkInterfaces = () => ({});
}

Place that code in a file and require it in webpack.config.js file.

We’re aware of this issue, and the fix will be pushed out soon, thanks.

@therealkenc Thanks for your feedback, what you are saying does make sense, we’ve decided to truncate the physical address length returned by lxcore to 16 bytes.

@cbier1 I’m running well on Windows 10 Creators Update 😁

Closing the issue out since it is fixed in the insider builds.

@buzinas Brilliant. I love you. I didn’t need to put it into a separate file, I just put it at the top of my Webpack config.

@Markus-ipse - we have not yet announced a release date beyond “Spring 2017”

https://www.microsoft.com/en-us/windows/upcoming-features

@russalex Just updated to 14986 and I can confirm that the issue is no longer present. (Node v7.0.1)