Closed dcousens closed 6 years ago
@miketwenty1 if this is your problem, I guess we'll find out. See #25
Unfortunately that didn't seem to solve what ever hangup Runkit is having with this package... I have no idea.. it's just frustrating to demo Bitcoinjs this way and having to go back to v3.x.x
@miketwenty1 what exactly is the error you get?
I'm not getting an error. Runkit is failing to find the package for some reason. I'm just confused about it.
Report it as missing then? Why is that a problem with this package?
To be Honest I'm not sure if there is a problem with this package or not. I've reported it missing here and there for the last couple weeks.. nothing has come of it.
I just found it weird as npm's main page practically now has runkit built into it, (You would think it would be reliable). Hence my original confusion about this.. and even more confusion.. the parent "bigger" package is easily found by runkit. Feel free to close this, I was just here to watch a miracle happen if you added a description.
@miketwenty1 the description hasn't been added yet, wait for the PR to be merged + released
@miketwenty1 check in a few minutes, I'll be happy for you if it fixed :+1:
didn't seem to fix anything :( Posted here: https://discuss.runkit.com/t/whoops-should-we-have-tiny-secp256k1-yes-please/1133
Hopefully they can figure it out.
I'm very confused about this NPM package. Why does it fail to show up on runkit? is it possible along with no description there is something odd/off about this npm package? https://npm.runkit.com/tiny-secp256k1 Runkit seems to have everything else except this npm package.
Edit: https://npm.runkit.com/secp256k1 The "tiny" version used in Bitcoinjs doesn't work but the original one seems to be fine with Runkit.