Running cnpm install reports an error

clipboard.png
error content: Error: write after end (writeStream "error") (writeStream "error"), GET https://cdn.npm.taobao.org/se. 200( connected: true, keepalive socket: false, agent status: {" createSocketCount ": 30," createSocketErrorCount ": 0," closeSocketCount ": 29," errorSocketCount ": 0," timeoutSocketCount ": 2, "requestCount": 910, "freeSockets": {}, "sockets": {"cdn.npm.taobao.org:443:true::": 1}, "requests": {}})
headers: {"server": "Tengine", "content-type": "application/octet-stream", "content-length": "21159804", "connection": "keep-alive", "date": "Sat, 09 Jun 2018 12:10:51 GMT", "x-oss-request-id": "5B1BC3CBCDF474A8B9C3AA39", "accept-ranges": "bytes", "etag": "2E8378E1055BB0CD1EE11DF41232F8DF", "last-modified": "Thu, 10 May 2018 10:07:51 GMT", "x-oss-object-type": "Normal", "x-oss-hash-crc64ecma": "2304935485797239861", "x-oss-storage-class": "Standard", "cache-control": "max-age=0, s-maxage=86400", "content-md5": "LoN44QVbsM0e4R30EjL43w==", "x-oss-server-time": "9", "via": "cache5.l2et15 [0206-0dje H], cache16.l2et15 [1d0], vcache15.cn195 [0206-0dH], vcache12.cn195 [1d0]", "age": "943186", "x-cache": "HIT TCP_MEM_HIT dirn:8:66671994 mlen:0", "x-swift-savetime": "Sun, 10 Jun 2018 12:04:57 GMT", "x-swift-cachetime": "870364", "timing-allow-origin": "*", "eagleid": "77544d2015294894370737909e"}

at writeAfterEnd (_stream_writable.js:236:12)
at WriteStream.Writable.write (_stream_writable.js:287:5)
at IncomingMessage.ondata (_stream_readable.js:639:20)
at emitOne (events.js:116:13)
at IncomingMessage.emit (events.js:211:7)
at addChunk (_stream_readable.js:263:12)
at readableAddChunk (_stream_readable.js:250:11)
at IncomingMessage.Readable.push (_stream_readable.js:208:10)
at HTTPParser.parserOnBody (_http_common.js:139:22)
at TLSSocket.socketOnData (_http_client.js:440:20)
May I ask what"s going on? And then using npm install will always get stuck in a certain step. The card is stuck in the step of installing selenium-server@ ^ 3.0.1. I don"t know why it is urgent. I don"t know why running selenium-server@3.0.1 will get stuck.

Mar.20,2021
Menu