A general question, guys. Is anyone recently having problems with yarn? I have had to resort to npm install --save due to an error reading "there appears to be problems with your network connection" when running yarn, even with a timeout setting of 60000. I have googled it and it seems many other people seem to be having the same problem. The general jabberwockery solution suggested in this link [https://github.com/yarnpkg/yarn/issues/5259#issuecomment-379769451]) didn't work for me and my yarn-error.log reads
Error: https://registry.yarnpkg.com/rxjs/-/rxjs-6.2.2.tgz: ESOCKETTIMEDOUT
at ClientRequest.<anonymous> (C:\Program Files (x86)\Yarn\lib\cli.js:135306:19)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:106:13)
at ClientRequest.emit (events.js:208:7)
at TLSSocket.emitTimeout (_http_client.js:708:34)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:106:13)
at TLSSocket.emit (events.js:208:7)
at TLSSocket.Socket._onTimeout (net.js:407:8)
at ontimeout (timers.js:475:11)
This is not a Zero problem but I was wondering if anyone was experiencing similar problems and had found any work arounds?
3 Answer(s)
-
0
@BobIngham what is your yarn version ? I have 1.9.0-20180614.1131 and haven't faced such a problem before. It might be related to installed yarn version.
-
0
@ismcagdas - thanks for the reply. This ended up a re-install of Windows. I believe that Windows defender was blocking compiles and additions to node_modules folders . I added folder exceptions but I think all files were being locked and checked before being passed. I switched off Defender and the problem was lessened but there was still something not quite right. I decided to go for the nuclear option having lost two days work! Thanks for the interest and the input.
-
0
This ended up a re-install of Windows
:shock:
I hate such time killer problems.
