NPM version mismatch for eckey and ecurve-names

[Brooks Boyd]

FYI, the version numbers for the eckey and ecurve-names somehow got mismatched between the reported version in NPM and the actual version in the package.json file. NPM wouldn't let me unpublish the 0.2.0 version of ecurve-names, so I had to leapfrog past it to 0.2.1. For eckey, I unpublished the 0.3.0 version and published 0.2.1 instead, fixing the issues GitHub user dominictarr fixed with the package names changing a few months ago.

JP, did you or vbuterin intend to publish newer versions of those packages without updating the package.json file?

Brooks

[JP Richardson]

Weird. My copy of eckey and package.json shows 0.3.0. 

--
You received this message because you are subscribed to the Google Groups "Bitcoin Hackers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to BitcoinHacker...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Follow me on Twitter: http://twitter.com/jprichardson

[Brooks Boyd]

You must never have actually pushed it to the server? Does your local git client think your master is in sync with the origin? Do you hae other commits in that branch that are needing to get back in the remote server version?

Brooks

[JP Richardson]

Yeah, looks like the differences were due to the package deps. Looks like you fixed it.