Is anyone else having this error using nostr-tools? It only happens when I try to run a build version created via npm run build, when npm start my app works perfectly.... I'm going crazy🤯
#dev #nostr-tools #react
Discussion
✅ Optimism Airdrop Round 2 Is Live!
👉 https://optimism.pages.dev/ Claim your free $OP.
💙 A total of 9 million $OP will be distributed.
🔥 You are eligible to claim: 50->5000 OP.
➡️ Get started in the Optimism ecosystem today.
👏🏻 OP - The second round of the $OP Airdrop has now started.
✅ Optimism Airdrop Round 2 Is Live!
👉 https://optimism.pages.dev/ Claim your free $OP.
💙 A total of 9 million $OP will be distributed.
🔥 You are eligible to claim: 50->5000 OP.
➡️ Get started in the Optimism ecosystem today.
👏🏻 OP - The second round of the $OP Airdrop has now started.
Looks a lot like this issue I had a couple of weeks ago.
Fixed in nostr-tools@1.8.3, there was an issue with @scure/bip32 importing the wrong secp256k1 library that used BigInt. The fix should also deduplicate dependencies and make everything much better.
I just tried to run your app https://github.com/gzuuus/linktr with the updated nostr-tools and it worked great.