Support for private npm registries

[xpure-sklatt]

Hi,
we're using a private npm registry where authentication is required and we're struggling by fetching the version info from there.

At the moment it seems like next-update is using the .npmrc file to get the registry url, so I tried to put user and password into the url, like: https://user:[email protected] within my .npmrc file, but that still resulted in a timeout. Problem here is that https is always replaced by http, which is not supported by our registry.

I finally fixed it by editing your registry.js file (line 182):

// replaced this:
// npmUrl = npmUrl.replace(/^https:/, 'http:').trim()
// var url = npmUrl + escapeName(name)

// with this:
var user = encodeURIComponent('[email protected]');
var pass = encodeURIComponent('123abc?');
var registryBase = 'my-custom-registry.com/api/npm/';
var url = 'https://' + user + ':' + pass + '@' + registryBase + escapeName(name);

I also needed to increase the MAX_CHECK_TIMEOUT on line 313.

Is there a chance to implement a way of configuring a custom registry with custom credentials, https support and custom timeout value? We'd really love to use next-update in our project! It's a great tool!

[xpure-sklatt]

I forked next-update and implemented a solution that would work for our needs:
https://github.com/xpure-sklatt/next-update

It provides two additional parameters:

• --registry where you can define a custom registry url that is used for fetching the versions
• --check-version-timeout that lets you define a custom timeout for fetching versions

We are then running next-update like this:
next-update --check-version-timeout 100000 --registry https://me%40foo.bar:123abc%[email protected]/api/npm/

[Nxt3]

So our registry doesn't need authentication. I run the command like so:

next-update --registry=http://mycustomregistry.com

and still get:

npm ERR! This request requires auth credentials. Run npm login and repeat the request.

But I have no need for auth. Am I doing something wrong?