公告
财富商城
积分规则
提问
发文
2020-06-12 02:59发布
不美不萌又怎样
I tried to install a package with yarn earlier today and I got this
yarn install yarn install v1.9.4 [1/4]
i had a different error, but the same network connection issue. i read through this thread: https://github.com/yarnpkg/yarn/issues/15
and ended up uninstalling/reinstalling node/npm which fixed my issue. maybe there's something wrong with your node installation too?
If you are using WSL for linux just add the current ip domain in: C:\Windows\System32\drivers\etc\hosts e.g:
104.16.21.35 registry.yarnpkg.com
retrying few times worked out for me on similar issue.
I got this as well.
I ran yarn install --no-lockfile and it worked, so I deleted the node modules again and deleted yarn.lock. It looks like a bug in yarn, because yarn wasn't having issues in previous versions of my application.
yarn install --no-lockfile
yarn.lock
Try clearing your cache
cache
$ yarn cache clean $ yarn // to install dependencies, no need for "yarn install"
Approach 2
$ yarn install --network-timeout 1000000
Reference https://github.com/yarnpkg/yarn/issues/4890#issuecomment-358179301
Try increasing network timeout
yarn install --network-timeout 1000000
found this on GitHub issues https://github.com/yarnpkg/yarn/issues/4890
最多设置5个标签!
i had a different error, but the same network connection issue. i read through this thread: https://github.com/yarnpkg/yarn/issues/15
and ended up uninstalling/reinstalling node/npm which fixed my issue. maybe there's something wrong with your node installation too?
If you are using WSL for linux just add the current ip domain in: C:\Windows\System32\drivers\etc\hosts e.g:
retrying few times worked out for me on similar issue.
I got this as well.
I ran
yarn install --no-lockfile
and it worked, so I deleted the node modules again and deletedyarn.lock
. It looks like a bug in yarn, because yarn wasn't having issues in previous versions of my application.Try clearing your
cache
Approach 2
Reference https://github.com/yarnpkg/yarn/issues/4890#issuecomment-358179301
Try increasing network timeout
found this on GitHub issues https://github.com/yarnpkg/yarn/issues/4890