GitHub repo name and NPM package name mismatch

[khitrenovich]

I think that having GitHub repo named request-promise-retry (which is also mentioned in README) and publishing project to NPM as promise-request-retry is pretty confusing.

Note that NPM package named promise-request-retry actually exists and seems to be old and unmaintained. I've installed this one by mistake and it took me some time to figure it out.

I suggest to rename the repo to avoid such kind of confusions in the future. This seems to be a simple process - https://help.github.com/en/github/administering-a-repository/renaming-a-repository.

And thank you for publishing this useful project :)

[void666]

@khitrenovich thank you for pointing it out. Do you know if there can be impacts about publishing the same in npm, if we rename it?

[khitrenovich]

IIUC, npm registry does not really care about where the package is hosted. It's the content of your package.json (that is, package name and version) that matters.

Don't forget to update repo & bugs URLs there after the rename, though :)