Package name too similar to existing package node; try renaming your package to '@catpea/noxe

[catpea]

This is a feature request asking for using the same library that npm internally uses, and checking against the npm package database, to see if it triggers "too similar to existing package".

Otherwise npm-name/npm-name-cli works the same as npm info noxe.

And I wasn't trying to register something similar to node on purpose, I just think noxe is a fantastic name for a vpl, I ended up calling my package yutani.

And if this is too much work, then add a note to the readme that this works as well as npm info package, as in it does not do any string proximity checks.

Thanks.

[sindresorhus]

npm checks for similar package names server-side and they have not published exactly what they check for.

I had to disable the similiarity check we had because it kept hanging: 4e28036