C:\Users\Administrator>npm install -g npm
npm ERR! code ECONNREFUSED
npm ERR! errno ECONNREFUSED
npm ERR! FetchError: request to http://registry.npm.taobao.org/npm failed, reason: connect ECONNREFUSED 127.0.0.1:1080
npm ERR! at ClientRequest.req.on.err (D:\Program Files\nodejs\node_modules\npm\node_modules\node-fetch-npm\src\index.js:68:14)
npm ERR! at ClientRequest.emit (events.js:198:13)
npm ERR! at Socket.socketErrorListener (_http_client.js:392:9)
npm ERR! at Socket.emit (events.js:198:13)
npm ERR! at emitErrorNT (internal/streams/destroy.js:91:8)
npm ERR! at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
npm ERR! at process._tickCallback (internal/process/next_tick.js:63:19)
npm ERR! { FetchError: request to http://registry.npm.taobao.org/npm failed, reason: connect ECONNREFUSED 127.0.0.1:1080
npm ERR! at ClientRequest.req.on.err (D:\Program Files\nodejs\node_modules\npm\node_modules\node-fetch-npm\src\index.js:68:14)
npm ERR! at ClientRequest.emit (events.js:198:13)
npm ERR! at Socket.socketErrorListener (_http_client.js:392:9)
npm ERR! at Socket.emit (events.js:198:13)
npm ERR! at emitErrorNT (internal/streams/destroy.js:91:8)
npm ERR! at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
npm ERR! at process._tickCallback (internal/process/next_tick.js:63:19)
npm ERR! message:
npm ERR! ‘request to http://registry.npm.taobao.org/npm failed, reason: connect ECONNREFUSED 127.0.0.1:1080’,
npm ERR! type: ‘system’,
npm ERR! errno: ‘ECONNREFUSED’,
npm ERR! code: ‘ECONNREFUSED’,
npm ERR! stack:
npm ERR! ‘FetchError: request to http://registry.npm.taobao.org/npm failed, reason: connect ECONNREFUSED 127.0.0.1:1080\n at ClientRequest.req.on.err (D:\Program Files\nodejs\node_modules\npm\node_modules\node-fetch-npm\src\index.js:68:14)\n at ClientRequest.emit (events.js:198:13)\n at Socket.socketErrorListener (_http_client.js:392:9)\n at Socket.emit (events.js:198:13)\n at emitErrorNT (internal/streams/destroy.js:91:8)\n at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)\n at process._tickCallback (internal/process/next_tick.js:63:19)’ }
npm ERR!
npm ERR! If you are behind a proxy, please make sure that the
npm ERR! ‘proxy’ config is set properly. See: ‘npm help config’

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Administrator\AppData\Roaming\npm-cache_logs\2020-06-01T02_24_36_463Z-debug.log