Higher CPU load than webpack-dev-server?

[webpack]

Higher CPU load than webpack-dev-server?

[michaek]

This is a counterintuitive solution, as chokidar does list fsevents in optionalDependencies, and it was installed successfully in my project. Nonetheless, npm i --save-dev fsevents dropped my CPU use from 40% of a core to 0%.

[arobbins]

@michaek Worked for me as-well, thanks.

[index-swf]

I've had the same problem since I updated node, npm rebuild fsevents is also worked. Some packages need to be rebuilt after system upgrade. I wonder if webpack-dev-server should output a warn when it detects that fsevents is unavailable on Mac.
I apologize for my bad English.

[avioli]

Same here, although CPU usage at about 40%, not as high as 100%, but still not < 5%.

"express": "^4.13.3",
"webpack": "^1.12.2",
"webpack-dev-middleware": "^1.2.0",

Mac OS X 10.11.1, 2.5 GHz Intel Core i7, 16 GB 1600 MHz DDR3

webpack.config.js

[avioli]

... It's all because of the webpack watcher.

[eriknyk]

same problem, with a similar configuration of @avioli
cpu ~70%
any thoughts?

[mbektimirov]

I have about 100% on my CPU, memory is growing too. I tried to profile it with node-inspector but it was not that easy.

[sokra]

propably the native module for the watcher is not installed, so the watcher switch to polling mode, which is cpu intensive. Try to install the fsevents module for OS X, or increase the polling frequency.

[SpaceK33z]

Closing this issue because it's not related to this middleware. watchpack is related.

[sekoyo]

Thanks @michaek !!! Work proxy was freezing the install of fsevents and I was cancelling it, thinking nothing bad was happening

[nchase]

amazing. thank you, @michaek!