What can be the brakes of NodeJS?

Question

Node.js

I use node.JS + Grunt to automate front-end processes
Since I'm on Windows, I use cmder as a console
Problem: when a command is called, gruntthe console emulator freezes for a minute and a half, only then it starts displaying messages about the start and execution of processes (compiling less, auto-prefixing, merging media rules in CSS, and so on).
I can't imagine which way to dig? Why such a delay?
The task manager shows that during the delay, the node.exe process is doing something (6-10% CPU usage).

Answer 1

When a process is started in Windows, among other things, it can be checked by anti-virus software.

Answer 2

I'm a big fan of consoles and headlight development. Once there were similar brakes due to ConEmu, a new console with a node was created for a long time, but I can’t remember how I decided. Have you tried running it in regular cmd.exe and in powershell? You have to experiment and compare. Thanks for the tip on cmder, I'll try to use it, if I dig up something, I'll write it off.

Answer 3

Pretty strange behavior since I also use cmder (built on top of conEmu). Try, as mentioned above, through a regular console. I noticed with colleagues that sometimes cmder terribly slows down at startup, although I have never had this.