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

ng2-admin Webpack build stuck at 46% #688

Closed
tal-shahar opened this issue Feb 8, 2017 · 6 comments
Closed

ng2-admin Webpack build stuck at 46% #688

tal-shahar opened this issue Feb 8, 2017 · 6 comments

Comments

@tal-shahar
Copy link

[ ] bug report

report a bug

  • What is the current behavior?
    ng2-admin Webpack build stuck at 46%

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

  1. clone project from git.
  2. run npm install
  3. run npm start
  • What is the expected behavior?
    project node server ruining.

  • Please tell us about your environment:

  • Angular version: 2.0.0
  • linux Ubuntu 16.04
  • installed nodejs v7.5.0
  • installed npm v4.1.2
  • Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

image

lexzhukov pushed a commit that referenced this issue Feb 8, 2017
@lexzhukov
Copy link
Contributor

@tal-shahar, thanks for your bug report. This bug was fixed in d34e6e9.

@tal-shahar
Copy link
Author

tal-shahar commented Feb 8, 2017

still getting stuck in the same spot.
I'd like to point out this is apparently only happening on Ubuntu 16.04.

on Ubuntu 14.04 it works fine.

image

@tal-shahar
Copy link
Author

tal-shahar commented Feb 8, 2017

adding UV_THREADPOOL_SIZE=64 to npm start seems to have solved the issue.

@jezamba
Copy link

jezamba commented Feb 9, 2017

I tried adding adding UV_THREADPOOL_SIZE=64 to npm and the issue persist

@tal-shahar
Copy link
Author

@jezamba this is what I wrote in the terminal "UV_THREADPOOL_SIZE=64 npm start" when i ran the project, if that's what you did try increasing the number.
it has something to do with the number of threads allocated to the service, I'm not completely sure yet what it dose excellently, if anyone reading this knows i would love an explanation.

@john-landgrave
Copy link

@tal-shahar

You are a life saver. Thank you so much. At 3am last night I was about to throw my computer at a wall when I encountered this issue yet again and none of the previous tricks I had used worked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants