Open adrianmcli opened 5 years ago
I have contacted the author and this package is no longer maintained.
@ellis2323 So it should be marked as deprecated with suggested alternatives.
@filips123 Yes, sure but i'm not the author.
Note that scrypt is available in Node 10.x. No need to use a package:
Problem is that this package is currently used by many other packages. It should probably be updated to only use wrapper around Node.js 10 scrypt functions if they are available.
Is there a maintainer here ?
Please do a 1.x release of scrypt.js with code as-is. Anyone that depends on scrypt@^0.2.0
will never see 0.3.0
because ^
doesn't update with 0.x
versions, only works with 1.x.x
and above.
FYI Workaround:
use npm-force-resolutions
for force package-lock to resolve scrypt 0.3.0.
{
// in package.json
// …
"scripts": {
// …
"preinstall": "npx npm-force-resolutions"
},
"resolutions": {
"scrypt.js": "0.3.0"
},
// …
}
Also might need to make sure scrypt
is always an optional
dependency via manually adding "optional": true,
to the package-lock for any scrypt
not marked as such.
@axic another option that might help speed up adoption of 0.3.0
would be to deprecate 0.2.0
. It would still be installable, but the deprecation warnings might inspire packages to upgrade. Low cost but would help a lot.
typical abandonware, very cool!
is there anybody out there....
With Node 12, the underlying
scrypt
package fails to build. I was going to post my issue there, but that package's README states that it is a deprecated module and recommends other alternatives.Being that this current repo depends on
scrypt
so heavily, I figured it'd make the most sense to post an issue here.Do note that I have tried this with Node 11 and it built just fine.
How to test
Run the following under Node v12:
npm init -y
npm install scrypt.js
Notice that
scrypt
fails to build.Full log dump