7

Ever since upgrading to Visual Studio 2017, I have about five or six Node.js processes running and constantly taking up tons of CPU. This seems to happen mostly when debugging my ASP.NET website, and especially when compiling my Less and TypeScript files.

Frequently, just hitting Ctrl-S inside a Less file is enough to have Visual Studio stop responding for 20 seconds or more. This is extremely frustrating.

To be clear, this is not a Node.js project. I'm guessing that Visual Studio 2017 uses Node.js behind the scenes, perhaps for its Less and TypeScript compilation.

Is there any way to disable Node.js in Visual Studio 2017 and still have my TypeScript and Less files compile correctly?

Brian Rak
  • 4,912
  • 6
  • 34
  • 44
  • 1
    Also asked here: http://stackoverflow.com/questions/42769106/visual-studio-2017-node-js-server-process-turn-off – Glen Little Mar 15 '17 at 00:17
  • I hear ya man. Even my buddies that work at MSFT can't answer that question (or won't... what are they planning...) – Ryan Ternier Mar 15 '17 at 21:39
  • VS doesn't natively support compiling LESS files. How did you configure that? Are you using an extension, or maybe gulp tasks? – Jimmy Mar 16 '17 at 17:54
  • Also, as I commented in the thread posted by @GlenLittle, please file feedback about this through VS. There's a few different features that launch a Node process, and it'd be nice if we can narrow down which ones are causing this issue. – Jimmy Mar 16 '17 at 17:55
  • Can you also let me know the path to the node.exe process(es) that are spawning? I was able to repro this and filed a bug but I want to see if it's the same case as what you're running into. – Jimmy Mar 16 '17 at 19:57
  • One last question: how many instances of VS are you running at once? On my machine, I get 4 node processes from 1 instance of VS (one from the JS language service, 2 from web tools tasks, and 1 is a child process from one of the web tools ones). We should each (JS/web tools) be reusing our node instances so you shouldn't get more than these AFAIK. – Jimmy Mar 16 '17 at 20:33
  • @Jimmy, I'm super pumped that you were able to repro this and open a bug. Thank you! I'm using gulp to compile the LESS files, specifically the latest edition (3.3.0) of gulp-less. I have a total of five Node.js processes. One is at: C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\common7\ServiceHub\Hosts\ServiceHub.Host.Node.x86.exe. The other ones are all launched from: C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Web\External\node.exe. – Brian Rak Mar 16 '17 at 21:38
  • @Jimmy - I've some some info in the linked question. – Glen Little Mar 17 '17 at 05:05

0 Answers0