npm hangs

[jarrettj]

Note: for support questions, please use one of these channels: Chat: AngularClass.slack or Twitter: @AngularClass

• I'm submitting a ...
  [X] bug report
  [ ] feature request
  [ ] question about the decisions made in the repository
• Do you want to request a feature or report a bug?
  Bug
• What is the current behavior?
  Can't access in docker. It runs and configures itself. But I can't access it at http://127.0.0.1:8080
  or http://172.17.0.2:8080.
  Tried using vagrant as well. I get to the admin page, but then the entire vagrant VM freezes. It first hung at npm install. I reloaded and retried, now it constantly hangs at npm start.
• If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via
  Used the steps defined in docs
• What is the expected behavior?
  Access admin area.
• What is the motivation / use case for changing the behavior?
  N/A
• Please tell us about your environment:
  Mac Sierra.
• Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

Docker output:

Starting up http-server, serving dist
Available on:
  http://127.0.0.1:8080
  http://172.17.0.2:8080
Hit CTRL-C to stop the server

Vagrant output:
Nothing! It just hangs.

Regards.
JJ

[jarrettj]

Went as far as deleting my development vagrant VM and starting over. Here is what worked for me:

Increase VM memory and use NFS shared folder. Details can be found here https://stefanwrobel.com/how-to-make-vagrant-performance-not-suck.

Increasing the amount of inotify watchers (https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers):
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf ; sudo sysctl -p

Then I still had remnants of previous failures probably, because I had to do an npm cache clean as well.

Seems to work well now. :)