|
| 1 | +0 info it worked if it ends with ok |
| 2 | +1 verbose cli [ 'D:\\1.安装软件\\NodeJs\\node.exe', |
| 3 | +1 verbose cli 'D:\\1.安装软件\\NodeJs\\node_modules\\npm\\bin\\npm-cli.js', |
| 4 | +1 verbose cli 'search', |
| 5 | +1 verbose cli 'express' ] |
| 6 | +2 info using npm@3.10.10 |
| 7 | +3 info using node@v6.10.3 |
| 8 | +4 silly mapToRegistry name -/all |
| 9 | +5 silly mapToRegistry using default registry |
| 10 | +6 silly mapToRegistry registry https://registry.npmjs.org/ |
| 11 | +7 silly mapToRegistry data Result { |
| 12 | +7 silly mapToRegistry raw: '-/all', |
| 13 | +7 silly mapToRegistry scope: null, |
| 14 | +7 silly mapToRegistry escapedName: null, |
| 15 | +7 silly mapToRegistry name: null, |
| 16 | +7 silly mapToRegistry rawSpec: '-/all', |
| 17 | +7 silly mapToRegistry spec: '-/all', |
| 18 | +7 silly mapToRegistry type: 'local' } |
| 19 | +8 silly mapToRegistry uri https://registry.npmjs.org/-/all |
| 20 | +9 info updateIndex C:\Users\Administrator\AppData\Roaming\npm-cache\registry.npmjs.org\-\all\.cache.json |
| 21 | +10 verbose correctMkdir C:\Users\Administrator\AppData\Roaming\npm-cache correctMkdir not in flight; initializing |
| 22 | +11 warn Building the local index for the first time, please be patient |
| 23 | +12 silly update-index fetching https://registry.npmjs.org/-/all |
| 24 | +13 verbose request uri https://registry.npmjs.org/-/all |
| 25 | +14 verbose request no auth needed |
| 26 | +15 info attempt registry request try #1 at 16:57:10 |
| 27 | +16 verbose request id 4f8bd578020089c2 |
| 28 | +17 http request GET https://registry.npmjs.org/-/all |
| 29 | +18 info retry will retry, error on last attempt: Error: getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443 |
| 30 | +19 info attempt registry request try #2 at 16:57:32 |
| 31 | +20 http request GET https://registry.npmjs.org/-/all |
| 32 | +21 info retry will retry, error on last attempt: Error: getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443 |
| 33 | +22 info attempt registry request try #3 at 16:58:43 |
| 34 | +23 http request GET https://registry.npmjs.org/-/all |
| 35 | +24 verbose stack Error: getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443 |
| 36 | +24 verbose stack at errnoException (dns.js:28:10) |
| 37 | +24 verbose stack at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:76:26) |
| 38 | +25 verbose cwd E:\1.NodeStudy\高级的Node\first |
| 39 | +26 error Windows_NT 6.1.7601 |
| 40 | +27 error argv "D:\\1.安装软件\\NodeJs\\node.exe" "D:\\1.安装软件\\NodeJs\\node_modules\\npm\\bin\\npm-cli.js" "search" "express" |
| 41 | +28 error node v6.10.3 |
| 42 | +29 error npm v3.10.10 |
| 43 | +30 error code ENOTFOUND |
| 44 | +31 error errno ENOTFOUND |
| 45 | +32 error syscall getaddrinfo |
| 46 | +33 error network getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443 |
| 47 | +34 error network This is most likely not a problem with npm itself |
| 48 | +34 error network and is related to network connectivity. |
| 49 | +34 error network In most cases you are behind a proxy or have bad network settings. |
| 50 | +34 error network |
| 51 | +34 error network If you are behind a proxy, please make sure that the |
| 52 | +34 error network 'proxy' config is set properly. See: 'npm help config' |
| 53 | +35 verbose exit [ 1, true ] |
0 commit comments