Visual Studio 2017 npm error – CategoryInfo not specified

While trying to install and test the npm package node-adwords, I stumbled upon an error stating an error with CategoryInfo not being specified.

The errors given by npm included e.g. gyp error, and reading about it from random internet sources, the problem seemed to point to compiler settings. I updated node to the latest version, which did not resolve the issue.

The next attempt was to modify my Visual Studio 2017 Professional installation, and specifically the Node.js options:

nodejs-reintall-vs2017

I did not have the VC++ 2017 v141 toolset installed, so I ticked it along with Visual Studio C++ core features (I don’t think it is necessary) and started the installation.

Unfortunately it did not fix the problem either.

As I’m a consultant paid for results and not configuring, I’m not that interested in finding the correct or right way to fix such environmental issues. I only want a working solution – so I jumped to the final attempt to quickly fix the issue which was to uninstall Node support from Visual Studio 2017, and then to add it back again. That worked 🙂

 

 

Advertisements

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s