global add binaries sometimes don't appear, please error check and state full path with -v

[kylecordes]

This is using version 0.17.2. On Mac OS Sierra, but that doesn't matter here.

The current behavior is: in certain cases, which I've been unable to nail down, "yarn global add packagename" lists the name of a bin script, presumably as a claim that it has installed that been scrapped. After extensive investigation (searching the whole hard drive) the script is not present anywhere. I tested this on multiple NPM packages, including small simple ones, this is not a problem with a particular package but with yarn itself.

Expected behavior #1: In all cases (verbose or otherwise) use more aggressive error checking around the installation of bin scripts. Remove any possible paths by which yarn might claim in its message to the user that a script has been installed, but the script is not actually present.

Expected behavior #2: When I use -v, in addition to stating the name of the binary that was installed, state the exact full path at which it was installed. (This will assist with any user path set up problems, although it is irrelevant for the failure case I encountered because the script is not actually present anywhere.)

Of course there is really an underlying bug hiding here somewhere. Adding this enhancement will inevitably drag that bug out into the open where a more specific bug report can be filed and problem can be fixed. This enhancement would also reduce the likelihood of any similar bugs in the future, as well as enhance user confidence about what yarn is doing.

[kylecordes]

Looks like this is very similar to #1886 - that is the specific problem, this item is the way to fix that category of problem.