Provide feedback when scoped npm packages fail to publish accurately, related to #521

Heya! I've found the same bug between yarn and npm that many other individuals have, and would suggest better feedback in the CLI about this, until it is resolved (#521). As a part of this, I am only asking for feedback in the CLI about this issue until it's effectively resolved.

I've been trying to publish and checkout an npmjs package by using yarn. The package is private and scoped to my organization. This is the workflow that explicitly happens as a part of #521. It happens to both private and publicly scoped packages. Unfortunately, I sunk a ton of time into diagnosing this issue on my own, then @patrickkettner helped diagnose in an hour - faster than I obviously was able to.

The thing is, yarn is so much friendlier than npm - translating that, it means it's easier for less technical people to work with yarn. I accidentally spent a lot of time on trying to diagnose what's described in #521, when it could've been resolved immediately on the yarn publish command, by failing to publish the package, and/or providing the user with a link to the issue.

Do you want to request a feature or report a bug? This is a feature to support the experience of people hitting a bug.

What is the current behavior? Scoped packages published via npm are usable in projects. Scoped packages published via yarn cannot resolve, as the tgz file isn't created.

If the current behavior is a bug, please provide the steps to reproduce. Using NPM: running npm publish on the projects directory, after bumping the version number of the package, I'm able to go to a scratch directory, do npm init, then npm install @organization/organization-package and it and dependencies install just fine.

Using Yarn: running yarn publish on the projects directory, after bumping the version number of the package, I'm able to go to a scratch directory, do yarn init, then yarn add @organization/organization-package, what happens is the tgz file doesn't seem to be created. This is related to #521.

What is the expected behavior? I suggest supporting copy for people hitting this bug, copy that suggests that this is a bug that's being considered for resolution with the yarn publish command. Going further, as a kind of stretch goal, there could be a link to a workaround that verifiably works by the yarn maintainers or community.

Considering this issue has existed for people for about 6 months, it would be really valuable to communicate this issue sooner than later while it still exists.

Please mention your node.js, yarn and operating system version. node: v7.7.4 npm: 4.5.0 yarn: 0.21.3