search

yarnpkg / yarn

The 1.x line is frozen - features and bugfixes now happen on https://github.com/yarnpkg/berry
https://classic.yarnpkg.com
Other
41.44k stars 2.73k forks source link

yarn fails to find packages, npm succeeds #5989

Open kaitlynbrown opened 6 years ago

kaitlynbrown commented 6 years ago

Do you want to request a feature or report a bug? Bug

What is the current behavior? yarn fails to install certain packages, while npm has no problem installing them

If the current behavior is a bug, please provide the steps to reproduce. https://pastebin.com/NYpWdtzB https://pastebin.com/Vfhy3AJ0

What is the expected behavior? yarn should be able to install any package npm can install, and should succeed at running react-native init (I find it funny that when using npm, react-native init suggests to use yarn when the only reason I'm using npm is that yarn won't even work!)

Please mention your node.js, yarn and operating system version. Tried with versions 1.7.0, 1.8.0 and v1.9.0-20180612.1255 of yarn node v9.11.1 elementary OS Loki 0.4.1

Weird thing is, yarn seems to work fine when I'm at work. The only time it doesn't work is when I'm at home. I use the same computer at both places, the only difference is the network connection. I don't use any proxies or anything like that at either location.

kaitlynbrown commented 6 years ago

Any updates on this? Still happening regularly, and is really super annoying

kaitlynbrown commented 6 years ago

Still completely unable to use yarn at home because of this issue, a month and a half later. It's especially annoying because I also can't use crna, because with yarn installed I get these errors and without it installed, it still tries to use it and errors because it isn't installed.

Is there any further information I can provide to help debug the problem? Traceroutes, or something? Given that it happens while at home, but not when I'm at work (on the same computer), it seems like it must be some network-related issue that npm is able to recover from but yarn is not (npm still works totally fine, remember)