Suggest moving away from npm blake3 package

[jrayback]

The package has only 2,500 weekly downloads, and seems poorly maintained. An alternative to consider is @noble/hashes, which has 1.7 million weekly downloads, has a much better maintenance record, and is externally audited.

[AlexAndrei98]

Hey @jrayback I played a bit around with the nobles libraries and it looks like there is secp256r1 within @noble/curves

[AlexAndrei98]

I found this example of usage of secp256r1 in the did-jwt library here

[jrayback]

Oh, wow! Good catch! Thank you @AlexAndrei98 . I think the @noble library will be much better. I'll look at the example you sent through and include the migration to the new library in a PR resolving the other package dependency problems.

[jrayback]

@AlexAndrei98 , looks like you've already pushed a PR for this one. Thanks. I'll submit something today to handle the other package deps.

[AlexAndrei98]

@jrayback Thank you! Will try to fix the package-lock. I was looking at this while working on #15 .

[jrayback]

OK, @AlexAndrei98 , I'm actively working on handling the other packages:

• text-encoding (remove)
• urlsafe-base64 (remove in favor of native node.js capability)
• ecdsa-secp256r1 (replace with @noble/curves)
  I hope to have a PR ready for review by tomorrow's dev meeting.

[jrayback]

closed by #16