Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NG not found in WSL #3944

Closed
sGerli opened this issue Jan 11, 2017 · 4 comments
Closed

NG not found in WSL #3944

sGerli opened this issue Jan 11, 2017 · 4 comments

Comments

@sGerli
Copy link

sGerli commented Jan 11, 2017

OS?

Windows 10 using WSL

Versions.

1.0.0-beta.24

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

  1. Enable WSL in your windows installations.
  2. Update Node and NPM
  3. Run npm install -g angular-cli
  4. Try running ng help

Then try:
5. Try a workaround for this alias ng="/path/to/.npm-global/lib/node_modules/angular-cli/bin/ng"
6. Run ng help
7. And we see our error EINVAL: invalid argument, uv_interface_addresses

The log given by the failure.

EINVAL: invalid argument, uv_interface_addresses
Error: EINVAL: invalid argument, uv_interface_addresses
    at /mnt/c/Users/sGerli/.npm-global/lib/node_modules/angular-cli/node_modules/portfinder/lib/portfinder.js:395:23
    at Object.<anonymous> (/mnt/c/Users/sGerli/.npm-global/lib/node_modules/angular-cli/node_modules/portfinder/lib/portfinder.js:410:2)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/mnt/c/Users/sGerli/.npm-global/lib/node_modules/angular-cli/commands/serve.js:5:18)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
    at Class.includedCommands (/mnt/c/Users/sGerli/.npm-global/lib/node_modules/angular-cli/addon/index.js:22:16)
    at /mnt/c/Users/sGerli/.npm-global/lib/node_modules/angular-cli/ember-cli/lib/models/project.js:335:61
    at Array.forEach (native)
    at Project.addonCommands (/mnt/c/Users/sGerli/.npm-global/lib/node_modules/angular-cli/ember-cli/lib/models/project.js:334:15)
    at Project.eachAddonCommand (/mnt/c/Users/sGerli/.npm-global/lib/node_modules/angular-cli/ember-cli/lib/models/project.js:369:30)
    at module.exports (/mnt/c/Users/sGerli/.npm-global/lib/node_modules/angular-cli/ember-cli/lib/cli/lookup-command.js:33:13)
    at CLI.<anonymous> (/mnt/c/Users/sGerli/.npm-global/lib/node_modules/angular-cli/ember-cli/lib/cli/cli.js:43:26)
    at tryCatch (/mnt/c/Users/sGerli/.npm-global/lib/node_modules/angular-cli/node_modules/rsvp/dist/rsvp.js:538:12)
    at invokeCallback (/mnt/c/Users/sGerli/.npm-global/lib/node_modules/angular-cli/node_modules/rsvp/dist/rsvp.js:553:13)
    at publish (/mnt/c/Users/sGerli/.npm-global/lib/node_modules/angular-cli/node_modules/rsvp/dist/rsvp.js:521:7)
    at flush (/mnt/c/Users/sGerli/.npm-global/lib/node_modules/angular-cli/node_modules/rsvp/dist/rsvp.js:2373:5)
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
    at process._tickCallback (internal/process/next_tick.js:98:9)

Mention any other details that might be useful.

In this project we found a workaround for a similar issue pebble-dev/rebble-store#65 with WSL

@sGerli sGerli changed the title NGnot found in WSL NG not found in WSL Jan 11, 2017
@jemmaengz1202
Copy link

I have exactly the same issue, with the same platform.
There is no trouble with Windows cmd...

@sarunint
Copy link
Contributor

This is a known issue in WSL. See microsoft/WSL#1343 for more information.

It should be fixed when next version of Windows 10 is released.

@filipesilva
Copy link
Contributor

Closed as answered by @sarunint

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
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

4 participants