Skip to content

ng command hangs for Node v7.0.0 #2888

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

Closed
jtsom opened this issue Oct 25, 2016 · 5 comments · Fixed by #2846
Closed

ng command hangs for Node v7.0.0 #2888

jtsom opened this issue Oct 25, 2016 · 5 comments · Fixed by #2846

Comments

@jtsom
Copy link
Contributor

jtsom commented Oct 25, 2016

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

OS X Sierra 10.12.1
Homebrew 1.0.8-133-g84d1661

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

v1.0.0-beta.18 installed. Cannot run command, ng command hangs

Repro steps.

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

Type ng command. Nothing happens. Status bar in Terminal window shows: ng --version(node)

Have to Control-C to exit

The log given by the failure.

None.

Mention any other details that might be useful.


Thanks! We'll be in touch soon.

@jtsom
Copy link
Contributor Author

jtsom commented Oct 25, 2016

Ok, digging around, looks like it's a problem with watchman. I uninstalled that - after going back to Node 6.9.1 and ng still wasn't working, saw that watchman was trying to run. Uninstalling watchman seems to have worked.

@mixomat
Copy link

mixomat commented Oct 26, 2016

@jtsom thx, had the same issue 👍

@jtsom
Copy link
Contributor Author

jtsom commented Oct 26, 2016

Strange thing is, on another system, having Watchman installed is not causing any problems.

I can run Node 7 just fine with angular-cli without watchman on this system. Add watchman, and it hangs. (For what it's worth, the Ember cli command does the same - not surprising as they're similar)

@jtsom
Copy link
Contributor Author

jtsom commented Oct 26, 2016

More testing. I tried installing watchman again, and ng was still hanging.

This time I uninstalled watchman (brew uninstall watchman) and also removed the launchctl item (launchctl remove com.github.facebook.watchman) to make sure it was gone.

ng worked fine. So I reinstalled watchman and started up an angular 2 app - and it seems to be ok now. The launchctl item reinstalled itself - I can only assume something got corrupted?

YMMV

@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.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants