C:\Program Files (x86)\nodejs>npm install npm@latest -g –ca=””
npm ERR! Windows_NT 6.1.7601
npm ERR! argv “C:\\Program Files (x86)\\nodejs\\node.exe” “C:\\Program Files (x8
6)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js” “install” “npm@latest” “-g” “–c
npm ERR! node v4.5.0
npm ERR! npm v2.15.9
npm ERR! code SELF_SIGNED_CERT_IN_CHAIN
npm ERR! self signed certificate in certificate chain
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>
npm ERR! Please include the following file with any support request:
npm ERR! C:\Program Files (x86)\nodejs\npm-debug.log
Old versions of the npm client used a certificate authority (CA) file that was bundled into the client itself. This was previously necessary because the client used a self-signed SSL certificate (not a great idea, but history can’t be changed).
The bundled CA does not work with our latest SSL certificate, pushed out over the last few days. We knew this, but didn’t realize the number of people who now use npm in environments where updating npm is difficult or slow. We are rolling back to the older cert now, but since the registry is distributed by a global CDN this process is slower than we’d like, and we don’t want to break things (further) by rushing the process.
npm set strict-ssl false
npm i -g tfx-cli