Webpack-dev-server: constant 100% CPU usage with node v6.0.0

[1000hz]

Not sure if this is happening to anyone else, but when I try to run webpack-dev-server with node 6, it pegs my cpu until I kill the process. Older versions of node would only use 100% CPU during active compilations. This kills my battery life. It might also be related to a loader (I've got my suspicions about node-sass).

Anybody else running into this?

[mbroadst]

I'm more at like 20-35% steady cpu usage, still pretty awful. Only noticed when my lap started getting pretty hot 😄

[micky2be]

I have 100% of CPU with Node 5.x

[JeffAMcGee]

I'm seeing the same problem. I think it may be the same issue as https://github.com/webpack/webpack-dev-middleware/issues/40 .

In my grommet project which uses webpack-dev-server, the problem went away when I deleted my node_modules directory and reinstalled everything.

[nathanmarks]

I had 135% CPU with Node v6.3 -- reinstalling node_modules helped a TON. Thanks @JeffAMcGee

[vanwagonet]

Changing the node major version probably trips up the native fsevents, so does it fall back to pulling badly? Reinstalling fixed it for me as well.

[SpaceK33z]

Also see https://github.com/webpack/webpack-dev-middleware/issues/40.

[gbakernet]

Thanks for the tip

When I upgraded from node 6 to node 8, I had the same problem, excessive cpu usage.

Deleting node_modules and reinstalling was the solution.