Chris Veness

Is that implementors including himself? :)

I think Barry may have abandoned this project. If you are using Node.js v10.5.0+, you could try my [scrypt-kdf](https://www.npmjs.com/package/scrypt-kdf), which is a simple pure-JS wrapper around the native OpenSSL implementation...

This repo is no longer maintained. If you are using `scrypt.hash`, it is now available natively in the Node.js [crypto](https://nodejs.org/api/crypto.html#crypto_crypto_scrypt_password_salt_keylen_options_callback) module. If you are using `scrypt.kdf` / `scrypt.verifyKdf`, [scrypt-kdf](https://github.com/chrisveness/scrypt-kdf) is...

I think Barry may have abandoned this project. If you are using Node.js v10.5.0+, you could try my [scrypt-kdf](https://www.npmjs.com/package/scrypt-kdf), which is a simple pure-JS wrapper around the native OpenSSL implementation...

@jonhartnett if it's still of interest, [scrypt-async](https://www.npmjs.com/package/scrypt-async) can be used as a polyfill for the OpenSSL scrypt, to enable [scrypt-kdf](https://github.com/chrisveness/scrypt-kdf) to be used with Node.js prior to 10.5.0 – there...

@spursy this repo is no longer maintained: [scrypt-kdf](https://github.com/chrisveness/scrypt-kdf) is a very close replacement, providing a (promise-based) zero-dependency wrapper around the native Node.js _crypto_ OpenSSL implementation of `scrypt`, which you might...

@dbryan0516, @ml1nk if you are using Node [v10.5.0 (current)](https://nodejs.org/en/blog/release/v10.5.0/), scrypt has finally been released as part of the [crypto](https://nodejs.org/api/crypto.html#crypto_crypto_scrypt_password_salt_keylen_options_callback) module: I have written a zero-dependency npm module [scrypt-kdf](https://www.npmjs.com/package/scrypt-kdf) which you...

@demurgos are you referring to the 'localise error to this function' section ([L110](https://github.com/chrisveness/scrypt-kdf/blob/master/scrypt.js#L110))? My intention was to pass on all relevant error information without spurious stack trace data from deep...

@demurgos you are quite correct about L179. I've not been able to think of any case where that exception would get thrown, but I was lazy in ignoring it: I've...

@dwalintukan I can't think of any reason `crypto.scrypt` would be missing from Node.js v10.5.0: it sounds like the sort of territory where I resort to rebooting!