What I wasn’t aware of is that Visual Studio has it’s own version of NodeJs that is uses for Task Runner Explorer work by default. I would surmise that during a recent VS update, it updated that internal version to one that wasn’t compatible with the current structure of the project’s gulpfile and SASS build.
It took me a while to figure out what was going wrong, but the fix was relatively simple. You need to override the version of Node that Visual Studio is using and force it to use the same version that the command prompt uses. To do this, open up the External Web Tools configuration in Visual Studio’s Options. Under the “Locations of external tools”, add a line at the top that points to your local NodeJs install (the one the command prompt uses).
Restart Visual Studio and it should solve the problem.
Husband, father, gamer, developer, manager, writer, creative, blogger, model railroader, Buckeyes fan