mojangson vs node-mojangson

[deathcap]

The readme example uses the module name "mojangson"

var mojangson=require("mojangson");

but it is published as "node-mojangson":

https://www.npmjs.com/package/node-mojangson

Could be reconciled by updating the readme example to use node-mojang or republishing as mojangson. I'd favor the latter, https://www.npmjs.com/package/mojangson is available and NPM recommends against node- prefix naming in modules because it is implied: (note that the GitHub repository could still stay named as node-mojangson, since the context is less clear)

https://www.npmjs.com/package/node-mojangson

• Don't put "js" or "node" in the name. It's assumed that it's js, since you're writing a package.json file, and you can specify the engine using the "engines" field. (See below.)

[rom1504]

Yeah I meant to publish it as mojangson, and apparently didn't. What should I do about https://www.npmjs.com/package/node-mojangson though ? Just let it online like that ? Wouldn't that be confusing ?

[rom1504]

Well I followed the advice at http://stackoverflow.com/a/28841779 and did: npm deprecate node-mojangson@"<=0.1.1" "WARNING: This project has been renamed to mojangson. Install using mojangson instead."

Republishing as mojangson.

[deathcap]

Thanks!