os.networkInterfaces error in NodeJS / Yeoman #468

StfBauer · 2016-06-02T22:51:58Z

I managed to successfully install NodeJS, NPM and Yeoman. You see all installed components in the version below.

When create a new project and type.
yo <generator-name>
Everything works fine. A problem happens when I just try yo. Because Yeoman somehow tries to access the network interfaces of the operation system propably. This won't work on BashOnWindows because there is no network interface directly included in the Linux Sub System and just use the same network as the host one.

Am I completely wrong or can this be fixed in future releases? Thanx.

The text was updated successfully, but these errors were encountered:

sunilmut · 2016-06-02T23:10:43Z

@StfBauer - If you can grab a strace of the failing command 'yo', we can see where it is failing and if it is tripping on something that is currently unimplemented. Thanks for trying out WSL!

StfBauer · 2016-06-03T12:15:10Z

@sunilmut Thank you. Attached the strace to this comment. Hope you find something useful.

Thanx for your great work so far. Love this.

yeoman-error.txt

sunilmut · 2016-06-03T18:19:48Z

socket(PF_NETLINK, SOCK_RAW, 0) = -1 EINVAL (Invalid argument)
WSL currently does not support NETLINK sockets. We are using our user voice page to prioritize the things to implement next. Please feel free to up vote this relevant task.

StfBauer · 2016-06-03T20:13:54Z

@sunilmut Thank you for the update. This will be required for the new SharePoint Framework update released by Microsoft. Because it use Yeoman generator to extend SharePoint from Linux, MacOSX as well as Windows.
In this case it would be great to use it from Bash On Windows.
Will add a user voice.

StfBauer · 2016-06-04T17:02:08Z

Added entry to user voices:
https://wpdev.uservoice.com/forums/266908-command-prompt-console-bash-on-ubuntu-on-windo/suggestions/14605521-add-netlink-socket-support

cadupedroni · 2016-06-15T22:25:29Z

I had a similar problem when trying to run the ionic.

Error getting IPv4 address: Error: EINVAL: invalid argument, uv_interface_addresses (CLI v1.7.15)

abhishek1214 · 2016-06-29T16:48:43Z

Has this been fixed?

abhishek1214 · 2016-06-29T16:49:27Z

Cause i am facing the same issue here is my error log

[22:09:50] Requiring external module babel-core/register
/mnt/c/Users/abhis/WebProjects/emails/cts-report/node_modules/browser-sync/node_modules/dev-ip/lib/dev-ip.js:21
var networkInterfaces = require("os").networkInterfaces();
^

Error: EINVAL: invalid argument, uv_interface_addresses
at Error (native)
at getIp (/mnt/c/Users/abhis/WebProjects/emails/cts-report/node_modules/browser-sync/node_modules/dev-ip/lib/dev-ip.js:21:43)
at Object. (/mnt/c/Users/abhis/WebProjects/emails/cts-report/node_modules/browser-sync/lib/utils.js:4:38)
at Module._compile (module.js:541:32)
at Module._extensions..js (module.js:550:10)
at Object.require.extensions.(anonymous function) as .js
at Module.load (module.js:458:32)
at tryModuleLoad (module.js:417:12)
at Function.Module._load (module.js:409:3)
at Module.require (module.js:468:17)
Error: [email protected] start: gulp
Exit status 1
at EventEmitter. (/usr/lib/node_modules/foundation-cli/node_modules/npm/lib/utils/lifecycle.js:217:16)
at emitTwo (events.js:106:13)
at EventEmitter.emit (events.js:191:7)
at ChildProcess. (/usr/lib/node_modules/foundation-cli/node_modules/npm/lib/utils/spawn.js:24:14)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at maybeClose (internal/child_process.js:852:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)

nicole-ashley · 2016-06-30T02:46:30Z

@StfBauer: I don't know for sure, but could the UserVoice suggestion you created be a duplicate of https://wpdev.uservoice.com/forums/266908-command-prompt-console-bash-on-ubuntu-on-windo/suggestions/13383789-enable-network-interface-enumeraration?

JWo1F · 2016-07-01T21:15:26Z

Hi! When it will be done? :)

sunilmut · 2016-07-05T15:56:41Z

We are looking into supporting NETLINK and RAW sockets. It's difficult to give any ETA at the moment.

afdallah · 2016-07-19T03:44:28Z

I'm also facing the same problem when i run gulp. Is there any solution?

simonbuchan · 2016-07-22T05:02:49Z

Just a note on current build 14393 this now gets to the bind call

socket(PF_NETLINK, SOCK_RAW, 0)         = 9
bind(9, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = -1 EINVAL (Invalid argument)

nicole-ashley · 2016-07-22T05:14:42Z

Woohoo, progress! Soon I'll be able to switch to WSL for my node apps

simonknittel · 2016-07-31T09:45:30Z

Just wanna say, that BrowserSync propably fails because of the same reason:

/mnt/e/wsl/repos/static-site-generator/node_modules/dev-ip/lib/dev-ip.js:21
    var networkInterfaces = require("os").networkInterfaces();
                                          ^

Error: EINVAL: invalid argument, uv_interface_addresses
    at Error (native)
    at getIp (/mnt/e/wsl/repos/static-site-generator/node_modules/dev-ip/lib/dev-ip.js:21:43)
    at Object.<anonymous> (/mnt/e/wsl/repos/static-site-generator/node_modules/browser-sync/lib/utils.js:4:38)
    at Module._compile (module.js:541:32)
    at Module._extensions..js (module.js:550:10)
    at Object.require.extensions.(anonymous function) [as .js] (/mnt/e/wsl/repos/static-site-generator/node_modules/babel-register/lib/node.js:156:7)
    at Module.load (module.js:458:32)
    at tryModuleLoad (module.js:417:12)
    at Function.Module._load (module.js:409:3)
    at Module.require (module.js:468:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/mnt/e/wsl/repos/static-site-generator/node_modules/browser-sync/lib/snippet.js:9:20)
    at Module._compile (module.js:541:32)
    at Module._extensions..js (module.js:550:10)
    at Object.require.extensions.(anonymous function) [as .js] (/mnt/e/wsl/repos/static-site-generator/node_modules/babel-register/lib/node.js:156:7)
    at Module.load (module.js:458:32)

Everything is up-to-date (Windows, BrowserSync, Node, ...)

Codenator81 · 2016-07-31T12:51:22Z

@simonknittel Yes still not work for me.

afdallah · 2016-08-01T13:59:23Z

Same here, i've update to the recent build. still get this error

mikeesouth · 2016-08-03T09:52:59Z

Any news on this? Any workaround? This is causing my webpack builds to fail.

miladmostavi · 2016-08-03T10:10:42Z

We do not need raw sockets, rather, just the ability to query what interfaces there are.. Any updates on this?

abergs · 2016-08-03T12:27:09Z

Yep, I'm watching this as well. Breaking for me with the package "node-sass".
Running "Bash on Ubuntu on Windows" in the Anniversary Update.

aseering · 2016-08-03T13:46:52Z

I've hit the issue with os.networkInterfaces(), and I've found a workaround (though it's ugly):

Look at the stack trace to determine what direct package is causing this issue. Note that it's probably not the package that you're trying to run; it's probably a dependency of that package. @StfBauer , it looks like your problem is in npmconf (same as me). @abhishek1214 @simonknittel @afdallah , it looks like all of you are hitting a problem in the dev-ip module.
Look inside ~/.npm/<packagename>/<version>/. (If multiple versions are available, you probably want to update all of them? Though for me there was only one version.) You should see a directory named package and a file named package.tgz
Look inside the directory named package; you should be able to find the exact .js file where the failure in your stack trace is occurring. Make a backup copy of that file somewhere so you can revert your changes if necessary.
Open that file in your favorite Linux text editor. Replace all calls to os.networkInterfaces(), require("os").networkInterfaces(), etc with just {}. (Do this intelligently, not blind search-and-replace -- make sure the file continues to be syntactically-valid JavaScript.) This will cause the script to not see metadata for any network interfaces, which might cause problems in some applications, but WSL isn't providing that metadata right now anyway.
Save the file. Exit your text editor.
Run cd .. as necessary to get yourself back to ~/.npm/<packagename>/<version>/. Run the following command to re-create the .tgz file: tar czvf package.tgz package
Go back to your project. Re-run npm install. You might need to remove your whole node_modules directory and reinstall.

Anyway, I think that gets all the steps? This is definitely not a polished solution; it would be great if someone with a little more node experience than I could give it a try and report back on what other hackery they needed to do.

george-cz · 2016-08-03T16:26:32Z

@aseering unfortunately, this isn't a workaround, nor fix, since it breaks the application. Its like saying "when your car doesn't steer correctly, remove the steering wheel"

neoadventist · 2016-08-03T16:28:14Z

If only I can get this working then I can watch the files for when my test changes then I can be golden!

calderhayes · 2016-08-03T16:35:31Z

+1

aseering · 2017-03-20T19:34:33Z

Hi @micahblu -- thanks for posting, but it's a long thread in part because people keep asking questions that have already been answered :-) So I hope you'll understand if I give you a brief answer and direct you to go read the thread.

In short: This problem has been fixed for a while now. The fix is only available in Insider builds, which are much newer than build 14393.

The fix is not being backported; it will ship with the next major version of Windows, which is due out in a few months. There's lots of discussion about all of this above.

micahblu · 2017-03-20T22:19:38Z

Thanks!

mikaturk · 2017-03-30T12:23:44Z

@aseering Will this be fixed in the creators update?
https://blogs.windows.com/windowsexperience/2017/03/29/windows-10-creators-update-coming-april-11-surface-expands-markets/#y78c8ro81mrI2dXQ.97
because if so, the fix is less than 2 weeks out :D

mateusmedeiros · 2017-03-30T12:54:19Z

@mikaturk It will. It has been fixed for us using insider buils for some good time now.

sunilmut · 2017-03-30T19:48:14Z

@mikaturk

Will this be fixed in the creators update?

Yes, it will be.

serbanghita · 2017-04-01T09:06:02Z

I'm waiting for the fix. Meanwhile I switched temporary to git bash for Windows in order to run my node builds. I still have high hopes for Windows Subsystem for Linux feature.

feryardiant · 2017-04-06T04:22:01Z

As per @nmai & @saschagehlich said, I've tried this command

> netsh interface teredo set state disabled

On cmd (as Administrator), but still got no luck with either ip addr show and ifconfig

$ feryardiant at MIMIN-ZENBOOK in ~
[11:13:10] → ip addr show
SO_SNDBUF: Invalid argument

$ feryardiant at MIMIN-ZENBOOK in ~
[11:13:13] → ifconfig
Warning: cannot open /proc/net/dev (Tidak ada berkas atau direktori seperti itu). Limited output.

And still having same issue on node js

EINVAL: invalid argument, uv_interface_addresses

Did I need to completely reinstall WSL again? or reboot my PC? or what? 😅

Windows 10 Home 1607 build 14393.969

benhillis · 2017-04-06T04:25:09Z

You are still on Anniversary Update, could you install Creators Update and try again?

feryardiant · 2017-04-06T04:27:07Z

Is the Creators Update already released publicly? or I need to join Windows Insider first?

Thanks for your fast reply @benhillis

feryardiant · 2017-04-06T04:28:49Z

No updates yet, unfortunately

benhillis · 2017-04-06T04:29:10Z

Yes you can download now: https://www.microsoft.com/en-us/software-download/windows10ISO

feryardiant · 2017-04-06T04:31:04Z

Okay @benhillis, I'll try it and will back to you.

feryardiant · 2017-04-06T05:45:08Z

I can confirm that Creators Update is solve the issue. ifconfig and ip addr show works just fine,

$ feryardiant at Mimin-Zenbook in ~
[12:38:04] → ifconfig
eth1      Link encap:Ethernet  HWaddr 0a:00:27:00:00:02
          inet addr:192.168.56.1  Bcast:192.168.56.255  Mask:255.255.255.0
          inet6 addr: fe80::3411:3e51:18ca:2394/64 Scope:Unknown
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth2      Link encap:Ethernet  HWaddr 0a:00:27:00:00:07
          inet addr:192.168.99.1  Bcast:192.168.99.255  Mask:255.255.255.0
          inet6 addr: fe80::ac6f:9be5:bf8:2298/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Global
          UP LOOPBACK RUNNING  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wifi0     Link encap:UNSPEC  HWaddr 10-02-B5-52-3F-CD-00-00-00-00-00-00-00-00-00-00
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::f56d:7300:e95d:d95/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


$ feryardiant at Mimin-Zenbook in ~
[12:38:08] → ip addr show
8: eth0: <> mtu 1500 group default qlen 1
    link/ether 00:ff:ce:91:fd:d4
    inet 169.254.236.98/16 brd 169.254.255.255 scope global dynamic
       valid_lft forever preferred_lft forever
    inet6 fe80::347d:e364:27e4:ec62/64 scope global dynamic
       valid_lft forever preferred_lft forever
2: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 group default qlen 1
    link/ether 0a:00:27:00:00:02
    inet 192.168.56.1/24 brd 192.168.56.255 scope global dynamic
       valid_lft forever preferred_lft forever
    inet6 fe80::3411:3e51:18ca:2394/64 scope link dynamic
       valid_lft forever preferred_lft forever
7: eth2: <BROADCAST,MULTICAST,UP> mtu 1500 group default qlen 1
    link/ether 0a:00:27:00:00:07
    inet 192.168.99.1/24 brd 192.168.99.255 scope global dynamic
       valid_lft forever preferred_lft forever
    inet6 fe80::ac6f:9be5:bf8:2298/64 scope global dynamic
       valid_lft forever preferred_lft forever
1: lo: <LOOPBACK,UP> mtu 1500 group default qlen 1
    link/loopback 00:00:00:00:00:00
    inet 127.0.0.1/8 brd 127.255.255.255 scope global dynamic
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope global dynamic
       valid_lft forever preferred_lft forever
6: wifi0: <BROADCAST,MULTICAST,UP> mtu 1500 group default qlen 1
    link/ieee802.11 10:02:b5:52:3f:cd
    inet 192.168.1.2/24 brd 192.168.1.255 scope global dynamic
       valid_lft 86345sec preferred_lft 86345sec
    inet6 fe80::f56d:7300:e95d:d95/64 scope global dynamic
       valid_lft forever preferred_lft forever
4: wifi1: <> mtu 1500 group default qlen 1
    link/ieee802.11 10:02:b5:52:3f:ce
    inet 169.254.113.41/16 brd 169.254.255.255 scope global dynamic
       valid_lft forever preferred_lft forever
    inet6 fe80::81f2:d837:a9ec:7129/64 scope global dynamic
       valid_lft forever preferred_lft forever

also my npm run build is working now.

$ feryardiant at Mimin-Zenbook in personal/codes/laravel-project on git:testing ●
[12:41:56] → npm run build

> @ build /mnt/d/Workspaces/personal/codes/laravel-project
> node node_modules/cross-env/dist/bin/cross-env.js NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js

 95% emitting

 DONE  Compiled successfully in 14380ms                                                                      12:42:39
                                                                                                                       Asset       Size  Chunks                    Chunk Names
  assets/js/admin.js     301 kB       0  [emitted]  [big]  assets/js/admin
    assets/js/web.js     301 kB       1  [emitted]  [big]  assets/js/web
assets/css/admin.css   23 bytes    0, 0  [emitted]         assets/js/admin, assets/js/admin
  assets/css/web.css  519 bytes       0  [emitted]         assets/js/admin
   mix-manifest.json  194 bytes          [emitted]

Considering to remove babun from my PC 🤔

Thanks @benhillis

SFLAQiu · 2017-09-05T09:52:18Z

ubuntu apt-get install npm
run npm err
how to solve?
so bad

root@2NH7VYN4YAJPLYK:~# npm

/usr/share/npm/node_modules/npmconf/config-defs.js:322
Object.keys(os.networkInterfaces()).map(function (nic) {
^
Error: EINVAL, invalid argument
at getLocalAddresses (/usr/share/npm/node_modules/npmconf/config-defs.js:322:18)
at Object. (/usr/share/npm/node_modules/npmconf/config-defs.js:269:23)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/usr/share/npm/node_modules/npmconf/npmconf.js:4:18)
at Module._compile (module.js:456:26)
root@2NH7VYN4YAJPLYK:# /usr/bin/node --version
bash: /usr/bin/node: No such file or directory
root@2NH7VYN4YAJPLYK:#

mikaturk · 2017-09-05T12:45:35Z

@SFLAQiu
You need to apt-get install node first

aseering · 2017-09-05T14:14:12Z

@SFLAQiu -- what version of Windows do you have? (Run ver at a Windows Command Prompt, and copy/paste its output here.) Is it version 14393?

That particular error should have been fixed in Windows build 15007. You can get a newer version through Windows Update.

SFLAQiu · 2017-09-06T04:07:29Z

@aseering my windows os version is 14393,I'll try it out

SFLAQiu · 2017-09-06T04:08:06Z

@mikaturk I've installed node

SFLAQiu · 2017-09-06T04:12:02Z

have new question
I remove apt-get node and npm
then install nvm
nvm install success and nvm install stable already

root@2NH7VYN4YAJPLYK:/# nvm use 8
Now using node v8.4.0 (npm v5.3.0)
root@2NH7VYN4YAJPLYK:/# node -v
v8.4.0
root@2NH7VYN4YAJPLYK:/# npm -v
5.3.0
root@2NH7VYN4YAJPLYK:/# nvm list
-> v8.4.0
node -> stable (-> v8.4.0) (default)
stable -> 8.4 (-> v8.4.0) (default)
iojs -> N/A (default)
root@2NH7VYN4YAJPLYK:/#

but i restart bash，cmd node

root@2NH7VYN4YAJPLYK:/# node
The program 'node' can be found in the following packages:

node
nodejs-legacy
Try: apt-get install
root@2NH7VYN4YAJPLYK:/# node -v
The program 'node' can be found in the following packages:
node
nodejs-legacy
Try: apt-get install
root@2NH7VYN4YAJPLYK:/#

need again to nvm use
why？

phsantiago · 2017-11-19T21:41:26Z

Fixed in this release https://blogs.msdn.microsoft.com/commandline/2017/04/11/windows-10-creators-update-whats-new-in-bashwsl-windows-console/
Update your windows.

MukhtarAsorori · 2018-06-03T08:10:11Z

Is there any body can tell me how can fix this problem.
`D:\LSTU\LearnMySelf\web\Angular2\Angular2_GettingStarted\APM>npm start

[email protected] start D:\LSTU\LearnMySelf\web\Angular2\Angular2_GettingStarted\APM
tsc && concurrently "tsc -w" "lite-server"

node_modules/@angular/common/src/directives/ng_class.d.ts(48,34): error TS2304: Cannot find name 'Set'.
node_modules/@angular/compiler/src/aot/compiler.d.ts(44,32): error TS2304: Cannot find name 'Map'.
node_modules/@angular/compiler/src/compile_metadata.d.ts(342,20): error TS2304: Cannot find name 'Set'.
node_modules/@angular/compiler/src/compile_metadata.d.ts(344,28): error TS2304: Cannot find name 'Set'.
node_modules/@angular/compiler/src/compile_metadata.d.ts(346,15): error TS2304: Cannot find name 'Set'.
node_modules/@angular/compiler/src/compile_metadata.d.ts(348,23): error TS2304: Cannot find name 'Set'.
node_modules/@angular/compiler/src/compile_metadata.d.ts(350,17): error TS2304: Cannot find name 'Set'.
node_modules/@angular/compiler/src/compile_metadata.d.ts(352,25): error TS2304: Cannot find name 'Set'.
node_modules/@angular/compiler/src/output/output_ast.d.ts(433,63): error TS2304: Cannot find name 'Set'.
node_modules/@angular/core/src/change_detection/differs/default_keyvalue_differ.d.ts(24,15): error TS2304: Cannot find name 'Map'.
node_modules/@angular/core/src/change_detection/differs/default_keyvalue_differ.d.ts(28,16): error TS2304: Cannot find name 'Map'.
node_modules/@angular/core/src/di/reflective_provider.d.ts(87,123): error TS2304: Cannot find name 'Map'.
node_modules/@angular/core/src/di/reflective_provider.d.ts(87,165): error TS2304: Cannot find name 'Map'.
node_modules/@angular/core/src/facade/lang.d.ts(12,17): error TS2304: Cannot find name 'Map'.
node_modules/@angular/core/src/facade/lang.d.ts(13,17): error TS2304: Cannot find name 'Set'.
node_modules/@angular/platform-browser/src/browser/browser_adapter.d.ts(79,33): error TS2304: Cannot find name 'Map'.
node_modules/@angular/platform-browser/src/dom/dom_adapter.d.ts(97,42): error TS2304: Cannot find name 'Map'.
node_modules/@angular/platform-browser/src/dom/dom_renderer.d.ts(22,37): error TS2304: Cannot find name 'Map'.
node_modules/@angular/platform-browser/src/dom/shared_styles_host.d.ts(11,30): error TS2304: Cannot find name 'Set'.
node_modules/@angular/platform-browser/src/dom/shared_styles_host.d.ts(22,30): error TS2304: Cannot find name 'Set'.
node_modules/rxjs/Observable.d.ts(58,60): error TS2693: 'Promise' only refers to a type, but is being used as a value here.
node_modules/rxjs/Observable.d.ts(74,59): error TS2693: 'Promise' only refers to a type, but is being used as a value here.
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! [email protected] start: tsc && concurrently "tsc -w" "lite-server"
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Mukhtar\AppData\Roaming\npm-cache_logs\2018-06-03T08_09_19_261Z-debug.log

D:\LSTU\LearnMySelf\web\Angular2\Angular2_GettingStarted\APM>`

dreyks · 2018-06-03T08:32:42Z

update to the latest Node version

neurosnap mentioned this issue Jun 4, 2016

Bash on Windows os.networkInterfaces: EINVAL nodejs/node#7150

Closed

russalex added the feature label Jun 6, 2016

therealkenc mentioned this issue Jun 9, 2016

Graphic application support? #481

Closed

HWiese1980 mentioned this issue Jun 13, 2016

Python netifaces.interfaces() results in [Errno 22] Invalid argument #519

Closed

patricksrobertson mentioned this issue Jun 22, 2016

node-sass fails to install, due to os.networkInterfaces() EINVAL #567

Closed

therealkenc mentioned this issue Jul 17, 2016

Chrome fails to launch #648

Closed

aseering mentioned this issue Mar 24, 2017

ReactJS Application not starting #1805

Closed

therealkenc mentioned this issue Apr 2, 2017

var networkInterfaces = require("os").networkInterfaces(); ^ Error: EINVAL, invalid argument #1847

Closed

yeshuoer mentioned this issue Apr 30, 2017

Windows Subsystem for Linux 使用过程中的坑 yeshuoer/blog#3

Open

namel mentioned this issue May 23, 2017

HS256 not supported auth0-samples/auth0-angular-samples#30

Closed

gaearon mentioned this issue Jan 14, 2018

'Npm start' fails on react-scripts-start initial attempt facebook/create-react-app#3690

Closed

therealkenc added fixedinreleasebuild and removed fixedininsiderbuilds labels Jul 30, 2020

jeetiss mentioned this issue Mar 9, 2021

fix get-port sindresorhus/get-port#52

Closed

os.networkInterfaces error in NodeJS / Yeoman #468

os.networkInterfaces error in NodeJS / Yeoman #468

Comments

StfBauer commented Jun 2, 2016

sunilmut commented Jun 2, 2016

StfBauer commented Jun 3, 2016

sunilmut commented Jun 3, 2016

StfBauer commented Jun 3, 2016

StfBauer commented Jun 4, 2016

cadupedroni commented Jun 15, 2016

abhishek1214 commented Jun 29, 2016

abhishek1214 commented Jun 29, 2016

nicole-ashley commented Jun 30, 2016

JWo1F commented Jul 1, 2016

sunilmut commented Jul 5, 2016

afdallah commented Jul 19, 2016

simonbuchan commented Jul 22, 2016

nicole-ashley commented Jul 22, 2016

simonknittel commented Jul 31, 2016 • edited Loading

Codenator81 commented Jul 31, 2016

afdallah commented Aug 1, 2016

mikeesouth commented Aug 3, 2016

miladmostavi commented Aug 3, 2016 • edited Loading

abergs commented Aug 3, 2016 • edited Loading

aseering commented Aug 3, 2016

george-cz commented Aug 3, 2016

neoadventist commented Aug 3, 2016 • edited Loading

calderhayes commented Aug 3, 2016

aseering commented Mar 20, 2017

micahblu commented Mar 20, 2017

mikaturk commented Mar 30, 2017

mateusmedeiros commented Mar 30, 2017

sunilmut commented Mar 30, 2017

serbanghita commented Apr 1, 2017 • edited Loading

feryardiant commented Apr 6, 2017

benhillis commented Apr 6, 2017

feryardiant commented Apr 6, 2017

feryardiant commented Apr 6, 2017

benhillis commented Apr 6, 2017

feryardiant commented Apr 6, 2017

feryardiant commented Apr 6, 2017

SFLAQiu commented Sep 5, 2017 • edited Loading

mikaturk commented Sep 5, 2017

aseering commented Sep 5, 2017

SFLAQiu commented Sep 6, 2017

SFLAQiu commented Sep 6, 2017

SFLAQiu commented Sep 6, 2017 • edited Loading

phsantiago commented Nov 19, 2017

MukhtarAsorori commented Jun 3, 2018

dreyks commented Jun 3, 2018

simonknittel commented Jul 31, 2016 •

edited

Loading

miladmostavi commented Aug 3, 2016 •

edited

Loading

abergs commented Aug 3, 2016 •

edited

Loading

neoadventist commented Aug 3, 2016 •

edited

Loading

serbanghita commented Apr 1, 2017 •

edited

Loading

SFLAQiu commented Sep 5, 2017 •

edited

Loading

SFLAQiu commented Sep 6, 2017 •

edited

Loading