view private packages?

[trusktr]

It would be nice if there was a way to authenticate on unpkg with npm, so we can view private packages.

[mjackson]

I agree this would be a feature I'd like to add. We could possibly add the ability to log in to unpkg and paste an npm token so we would be able to let you browse private packages.

[felixfbecker]

And then the token could also be passed through the userinfo part of the URL to e.g. easily embed scripts locally with <script> when hacking on something for localhost.
Could custom registries also work, with a registry query parameter maybe?

[mjackson]

Just thinking about this a bit more ... if we were to serve private packages over a public CDN, we would probably need to prevent the CDN from caching them, otherwise people would be able to fetch the contents of private packages from the cache. This kind of defeats the point of using a CDN in the first place, since every request for a private package would bypass the cache.

It sounds to me like what you really want is the functionality of unpkg, but not the public CDN piece. Essentially a self-hosted version of unpkg (see #98). Is that right?

[mjackson]

Closing due to inactivity.

[j-avila]

This PR can solve this problem?