Ivan Herman on Nostr: npub1n5v3c…tf4kk In contrast to what the article says, crypto-js is now marked as ...
npub1n5v3c2glf2phlxw0wz4fg08rs045fd8mx3dsn3c2su2a393w0z6qwtf4kk (npub1n5v…f4kk) In contrast to what the article says, crypto-js is now marked as “discontinued” in npm.
Alternatives? One can use node’s internal crypto module, or use the WebCrypto API for portability (also available in node.js v21.* or in deno). The major downside of WebCrypto is that all functions are async (unless I missed something), and this “bubbles” to all your libraries that depended on crypto, as well as the users of those libraries. This, I am afraid, a major pain…
Alternatives? One can use node’s internal crypto module, or use the WebCrypto API for portability (also available in node.js v21.* or in deno). The major downside of WebCrypto is that all functions are async (unless I missed something), and this “bubbles” to all your libraries that depended on crypto, as well as the users of those libraries. This, I am afraid, a major pain…