Webpack frequently freezes when started

Ionic Framework ionic-v3
1

I’m developing an app using Ionic 2 rc3.

Sometimes webpack hangs when started. In this case I need to stop (CTRL+C) and run ionic serve again. And it’s a very frequent problem.

When I modify and save a file I get this message on terminal:

[13:22:59]  build started ...
[13:22:59]  transpile update started ...
[13:22:59]  transpile update finished in 18 ms
[13:22:59]  webpack started ...
3 Likes
2

the same problem for me, but frequence increases to pain…

Any Idea?

I’m on a Mac and my project increases also…

3

After some search I found that it’s a problem probably related to Webpack or Sass-loader.

4

No solutions with your researches ?

5

I also was thinking about webpack, more then about sassloader because
[xx:xx:xx] transpile update finished in 18 ms
[xx:xx:xx] webpack update started …
went
[xx:xx:xx] transpile update finished in 18 ms
[xx:xx:xx] webpack started …

anyone outside with some ideas?

I made a litle new app to make sure it’s not a problem of app-size:

no success :frowning:

6

sass update is launch only if we modify scss files.
I don’t do that and my webpack still freezing …

7

Same problem here… Any update on this?

8

Some topics about Webpack/Sassloadder hangings:




Some users says to change UV_THREADPOOL_SIZE. But I don’t know where it is.

9

I have the same problem.
Did someone solve it?

10

same problem for me…

executing env UV_THREADPOOL_SIZE=100 before running ionic serve -l did nothing - still crashing/freezing with webpack started ...

Your system information:

Cordova CLI: 6.4.0 
Ionic Framework Version: 2.0.0-rc.5
Ionic CLI Version: 2.1.18
Ionic App Lib Version: 2.1.9
Ionic App Scripts Version: 1.0.0
ios-deploy version: 1.9.0 
ios-sim version: 5.0.3 
OS: OS X El Capitan
Node Version: v7.2.0
Xcode version: Xcode 8.2.1 Build version 8C1002
11

Rolling node back to 6.9.4 (i.e. < 7) fixed it for me. I think it may have been an issue with the bundled version of node-sass and node 7.

1 Like
12

Apparently that worked for me too. Thank you so much!

1 Like
13

Recently I’ve got this error too:

MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 incremental_build_failed listeners added. Use emitter.setMaxListeners() to increase limit