-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide Hash utilities: Deno.hash / Deno.password #28277
Comments
Is it good to add specific Deno functionality rather than adding it to import { hash, password } from 'jsr:@std/crypto' |
Actually good, but does any packages in @std/ using wasm now? |
|
I thought put more things in Deno will provide slightly better DX. Since you don't need to import them (from internet). |
There are both pros and cons to putting things under the Deno namespace. Common pros are a native integration and the performance that comes with that. Common cons are bigger compile sizes, specially for those not making use of it, and locking in the features out of fear of breaking older scripts. |
Part of #28200
Deno.hash / Deno.password
In Node.js, we do hash like:
node:crypto
only have support for algorithm supported in openssl.But in nowadays, we may use more likely to use argon2, yescrypt for hashing passwords,
but those isn't in
node:crypto
, if we can justand
it will be more easier to use, and
implementation in native will also be faster.
(or maybe use wasm to avoid v8 internal binding costs)
The text was updated successfully, but these errors were encountered: