You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 6, 2024. It is now read-only.
We Windows users sometimes have issues with node-gyp which PeculiarVentures/node-webcrypto-ossl uses to build/install. They do have a another repo that is API comparable save a few algorithms that do not overlap between OSSL C++ & WebCrypto.
Also, seems that CloudFlare Workers use only WebCrypto API anyhow. Does it make sense to switch over to PeculiarVentures' WebCrypto for Node for (hopefully) faster & less bug-prone installs? Or is there another reason you prefer C++, like runtime performance? Or have the option for both?
Thanks for your project & consideration!
The text was updated successfully, but these errors were encountered:
tomByrer
changed the title
Use PeculiarVentures/webcrypto instead / also?
Use PeculiarVentures/webcrypto instead | also?
Jun 26, 2019
I'm all for switching to @peculiar/webcrypto. @ssttevee took a shot at it in #81 but we ran into an issue with the way cloudworker is architected that was a show stopper. Feel free to take a stab at it if you'd like!
We Windows users sometimes have issues with
node-gyp
which PeculiarVentures/node-webcrypto-ossl uses to build/install
. They do have a another repo that is API comparable save a few algorithms that do not overlap between OSSL C++ & WebCrypto.Also, seems that CloudFlare Workers use only WebCrypto API anyhow. Does it make sense to switch over to PeculiarVentures' WebCrypto for Node for (hopefully) faster & less bug-prone installs? Or is there another reason you prefer C++, like runtime performance? Or have the option for both?
Thanks for your project & consideration!
The text was updated successfully, but these errors were encountered: