Chore: Add end-to-end tests for private packages

[BYK]

We don't have e2e coverage for private packages which sometimes results in bugs going unnoticed until we make a release. We should have at least one smoke test for a very simple private package on NPM and private repo on GitHub or Bitbucket.

[onurtemizkan]

I can take this one if it's ok

[BYK]

@onurtemizkan go ahead and take it! The main issue here is who will own the test-related private packages? Looks like we can create a private repo under yarnpkg org and probably do the same with scoped packages on NPM but I'd rather hear what @bestander and @Daniel15 has to say about this first. Also may be @cpojer.

[bestander]

Yes, I think full e2e with private npm repo is the way to go. Whether it lives in yarnpkg it does not matter as long as we are fine with security.

…

On Wed, Aug 16, 2017 at 6:47 AM Burak Yiğit Kaya ***@***.***> wrote: @onurtemizkan <https://github.com/onurtemizkan> go ahead and take it! The main issue here is who will own the test-related private packages? Looks like we can create a private repo under yarnpkg org and probably do the same with scoped packages on NPM but I'd rather hear what @bestander <https://github.com/bestander> and @Daniel15 <https://github.com/daniel15> has to say about this first. Also may be @cpojer <https://github.com/cpojer> . — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4186 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACBdWIW2uVlGNmi0YcutTecF9NCmHoZgks5sYvLkgaJpZM4O46pg> .

[Daniel15]

I thought we already had an issue for this?

[BYK]

@Daniel15 - I couldn't find it. Feel free to close this or the other as a duplicate if you bump into it.

[bestander]

There was one but I did not create it, so can't find it.

[avindra]

Relevant breaking issue right now with private registry libs completely failing to install

#4157