'yarn why' breaks trying to find non-existent registry entry for private scoped lerna package.

[estaub]

I have a lerna monorepo, where lerna puts a symlink in the node_modules of a child package to depend on a sibling package. The subprojects are all private and scoped. When I try to perform

yarn why pg-promise (an unrelated package)

I get:

`An unexpected error occurred: "https://registry.yarnpkg.com/@semanterra%2fyeanay-server-shared: Not found".

The subprojects aren't registered anywhere; since they are private, I wouldn't think they would have to be.

yarn-error.log

[estaub]

This is a dupe of the unfixed (i.e., non-auth) aspects of #3755.

[rally25rs]

closing as duplicate

[estaub]

@rally25rs, Given that the issues raised in this were never addressed by the fix to #3755, which only addressed auth, I don't think closing it as a dupe makes much sense. If you mean to say "we're not going to address this", that's different.

[aewing]

This is incredibly irritating, and currently preventing most operations that should really have no reason to fail when unable to resolve a remote... Perhaps an option to ignore these errors from a given org would suffice...