Support for different npm package name

[bhanuc]

Currently the updater uses the application name to get the updates but since a library is already registered under my application's name, I wish to push my application under a different package name instead of managing a private npm server. I can do a PR as I think only few changes are to be made in index.js, lib/check.js and command.js are required it seems.

[justinmchase]

You're going to have to change the name then, in that case. You can consider getting private npm which will allow you to add a scope to the name.

[bhanuc]

I see a simple solution to add a url in the package.json file or add it in the function definition, if defined the new values would be used in constructing the url in update.js and check.js files else the default code would run. Would you guys be open to this small addition.

[justinmchase]

I don't understand the purpose though. You would still have to have a uniquely named project in order to upload it to npm. If you have a uniquely named project then it will already work.

You can override a package who's name is already taken by using your own private npm though.