| 12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152 |
- 0 verbose cli D:\node\node.exe D:\node\node_modules\npm\bin\npm-cli.js
- 1 info using npm@10.9.2
- 2 info using node@v22.14.0
- 3 silly config load:file:D:\node\node_modules\npm\npmrc
- 4 silly config load:file:C:\Users\21410\.npmrc
- 5 silly config load:file:D:\新建文件夹\naokong\myapp\node-global\etc\npmrc
- 6 verbose title npm install @angular/cli@latest
- 7 verbose argv "install" "--global" "@angular/cli@latest"
- 8 verbose logfile logs-max:10 dir:D:\新建文件夹\naokong\ node-cache\_logs\2025-05-22T12_32_42_998Z-
- 9 verbose logfile D:\新建文件夹\naokong\ node-cache\_logs\2025-05-22T12_32_42_998Z-debug-0.log
- 10 silly packumentCache heap:4345298944 maxSize:1086324736 maxEntrySize:543162368
- 11 silly logfile start cleaning logs, removing 1 files
- 12 silly packumentCache corgi:https://registry.npmmirror.com/@angular%2fcli cache-miss
- 13 silly logfile done cleaning log files
- 14 http fetch GET https://registry.npmmirror.com/@angular%2fcli attempt 1 failed with ETIMEDOUT
- 15 http fetch GET https://registry.npmmirror.com/@angular%2fcli attempt 2 failed with ETIMEDOUT
- 16 http fetch GET 200 https://registry.npmmirror.com/@angular%2fcli 205348ms attempt #3 (cache miss)
- 17 silly packumentCache corgi:https://registry.npmmirror.com/@angular%2fcli set size:292830 disposed:false
- 18 silly idealTree buildDeps
- 19 silly fetch manifest @angular/cli@19.2.13
- 20 silly packumentCache full:https://registry.npmmirror.com/@angular%2fcli cache-miss
- 21 silly placeDep ROOT @angular/cli@ OK for: want: 19.2.13
- 22 verbose type system
- 23 verbose stack FetchError: Invalid response body while trying to fetch https://registry.npmmirror.com/@angular%2fcli: read ECONNRESET
- 23 verbose stack at D:\node\node_modules\npm\node_modules\minipass-fetch\lib\body.js:170:15
- 23 verbose stack at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
- 23 verbose stack at async Response.json (D:\node\node_modules\npm\node_modules\minipass-fetch\lib\body.js:75:17)
- 23 verbose stack at async RegistryFetcher.packument (D:\node\node_modules\npm\node_modules\pacote\lib\registry.js:98:25)
- 23 verbose stack at async RegistryFetcher.manifest (D:\node\node_modules\npm\node_modules\pacote\lib\registry.js:128:23)
- 23 verbose stack at async #fetchManifest (D:\node\node_modules\npm\node_modules\@npmcli\arborist\lib\arborist\build-ideal-tree.js:1202:20)
- 23 verbose stack at async #nodeFromEdge (D:\node\node_modules\npm\node_modules\@npmcli\arborist\lib\arborist\build-ideal-tree.js:1040:19)
- 23 verbose stack at async #buildDepStep (D:\node\node_modules\npm\node_modules\@npmcli\arborist\lib\arborist\build-ideal-tree.js:904:11)
- 23 verbose stack at async Arborist.buildIdealTree (D:\node\node_modules\npm\node_modules\@npmcli\arborist\lib\arborist\build-ideal-tree.js:181:7)
- 23 verbose stack at async Arborist.reify (D:\node\node_modules\npm\node_modules\@npmcli\arborist\lib\arborist\reify.js:131:5)
- 24 error code ECONNRESET
- 25 error syscall read
- 26 error errno ECONNRESET
- 27 error network Invalid response body while trying to fetch https://registry.npmmirror.com/@angular%2fcli: read ECONNRESET
- 28 error network This is a problem related to network connectivity.
- 28 error network In most cases you are behind a proxy or have bad network settings.
- 28 error network
- 28 error network If you are behind a proxy, please make sure that the
- 28 error network 'proxy' config is set properly. See: 'npm help config'
- 29 silly unfinished npm timer reify 1747917163486
- 30 silly unfinished npm timer reify:loadTrees 1747917163492
- 31 verbose cwd D:\新建文件夹\naokong
- 32 verbose os Windows_NT 10.0.26100
- 33 verbose node v22.14.0
- 34 verbose npm v10.9.2
- 35 verbose exit 1
- 36 verbose code 1
- 37 error A complete log of this run can be found in: D:\新建文件夹\naokong\ node-cache\_logs\2025-05-22T12_32_42_998Z-debug-0.log
|
