[0.17.0] Cannot add module from github

[ElvisChiang]

Do you want to request a feature or report a bug?
Bug
What is the current behavior?

error An unexpected error occurred: "ENOENT: no such file or directory, lstat '/Users/elvis/Library/Caches/Yarn/npm-@remobile/react-native-toast-1.0.5-9eb744c751fe94b745a38fa4ae8f2de2d5ff4100'".

If the current behavior is a bug, please provide the steps to reproduce.

yarn add github:elvischiang/react-native-toast

What is the expected behavior?
There should be a folder named

~/Library/Caches/Yarn/npm-@remobile/react-native-toast-1.0.5-<HASH>/

But yarn has only

~/Library/Caches/Yarn/npm-\@remobile/react-native-toast-1.0.5/

Please mention your node.js, yarn and operating system version.
node: v4.6.0
yarn: 0.17.0
macOS: 10.11.6

[Kimleang]

same issue here
try running yarn on a fresh Laravel project and it trying to install a package from

github:jeroennoten/webpack-stream#patch-1

and I got the follwing error

"ENOENT: no such file or directory, lstat '/Users/kimleang/Library/Caches/Yarn/npm-webpack-stream-3.2.0-d679c2f1f964b5abae4c1f29d5cb695115deec7b'"

and here is my Yarn cache directory

node: v6.9.1
npm: 3.10.8
yarn: 0.17.0
macOS: 10.12.1

[bjeanes]

I'm also getting this with all my GitHub packages. E.g.:

error An unexpected error occurred: "ENOENT: no such file or directory, lstat '/Users/bjeanes/Library/Caches/Yarn/npm-ExpandingTextareas-0.2.0-c8b5f4a63b99818343fd90653182da17e944236f'".

If I mv ~/Library/Caches/Yarn/npm-ExpandingTextareas-0.2.0{,-c8b5f4a63b99818343fd90653182da17e944236f}, then I can proceed. If I don't have the dependency of a new or changed git dependency in my cache already (with the sha in name) I get this error 100% of the time when it tries to link these dependencies.

[danielkcz]

I would say duplicate of my already reported #1829

[bjeanes]

Not necessarily. It seems likely that the bug in this issue is due to not interpolating the git sha into the directory and so probably git clone specific. That issue is referencing a non-git dependency (node-sass). Maybe they share an underlying issue but I don't think there's much to indicate that yet.

[danielkcz]

Sorry, my bad, I meant #1818

[bjeanes]

Ah yes, probably

[bestander]

Closing in favor #1818 then

[tanx]

I'm still getting this error with yarn 0.17.2 :(

[danielkcz]

@tanx Apparently changelog for 0.17.2 did not mention this to be fixed, so I am not even trying it.

[tanx]

@FredyC I tested again with 0.17.3 and the issue seems to be resolved now. Thanks everyone for your quick help!