“The CodeDom provider type Microsoft.VisualC.CppCodeProvider could not be found” exception

This problem happened when you build project/solution in Visual Studio. Generally caused when you have compile-able files in your Visual Studio solutions but VS could not understand it.
In my case, I have infamous ‘node_modules’ folder.

To solve this issue, in Windows Explorer, I right click on it ‘node_modules’ folder and select ‘Properties’, check ‘Hidden’ under Attributes.

You can also exclude the folder. In Visual Studio Solution Explorer, right click on ‘node_modules’ and select ‘Exclude From Project’.

More reading.


Basic Node JS and NPM Commands

Following are some useful commands for Node.js and NPM.


Display Node.js version.

$ node --version

Run local NPM package. If the package is installed globally, don’t need to use ‘node’ command.

$ node run <npm_package_command>


Display NPM version.

$ npm --version

Interactively create a package.json file.

$ npm init

Install package globally.

$ npm install -g <module(s)>;

Install package locally and save the dependency to package.json.

$ npm install <module(s)> --save-dev

Install package(s) based on package.json file in the current folder.

$ npm install

List global packages with depth = 0.

$ npm ls -g -depth=0

List global packages detail with depth = 0.

$ npm ls -gl -depth=0

List local packages with depth = 0.

$ npm ls -depth=0

List local packages detail with depth = 0.

$ npm ls -l -depth=0

Search the registry for packages matching the search terms.

$ npm search <module>

Update global packages.

$ npm update -g

Update local packages.

$ npm update

Uninstall global package.

$ npm uninstall -g &amp;lt;module(s)&amp;gt;

Uninstall local package.

$ npm uninstall &amp;lt;module(s)&amp;gt;

Run NPM tasks defined in ‘scripts’ section of ‘package.json’ file. ‘start’ and ‘test’ scripts don’t need ‘run’ command.

$ npm run <script_task>
$ npm start

NPM run scripts boilerplate: