BufferPut NPM Out of Date about bitcore HOT 10 CLOSED

I'll look into it. Thanks for reporting

from bitcore.

I just created a test project which requires bitcore from npm and the Address example from README runs smoothly. I've heard from @ryanxcharles that others were having problems with BufferPut too. Can you tell us what OS and example you were running?

from bitcore.

@maraoz This is exactly why I said the npm module needs updating, there was a breaking bug fixed in master that made all the examples not work (bar the address one)

from bitcore.

I see. We're trying to get more people to have publish permissions to bitcore's npm so we accelerate this whole process. Thanks for your help!

from bitcore.

We just updated bitcore on npm, but if I read correctly, it is bufferput that is problematic. Correct? We'll need @gasteve to update npm for that.

from bitcore.

We have some version conflicts with bufferput. The version on BitPay GitHub is 0.1.1, but has code committed more recently than the 0.1.2 that is on npm. I suppose I could merge one into the other, update the version number, and then see if @gasteve can put that one on npm.

from bitcore.

Actually there are no differences in the index.js between the npm and bitpay github versions of bufferput, so there can't be any fixes in one that aren't in the other. If someone can figure out if there are any issues with the bitpay github bufferput, and issue a pull request that fixes it, then we can get the npm updated.

from bitcore.

784e4e3

from bitcore.

So, there's no problem then. FWIW I just tested the block monitoring example by installing bitcore fresh from npm and did not have any bufferput issues.

from bitcore.

Ah, I missed the bit where you said 'we just updated bitcore on npm' - my bad.

from bitcore.