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 Oct 30, 2024. It is now read-only.
The package fails to build in last released version and it prevents to npm install projects having that or THIS package in dependencies: web3/web3.js#3408 (comment)
(I had the same build issue on Fedora Linux in app with keythereum dependency - the scrypt was failing to build.)
But that is pretty complicated if your package depends indirectly, like through keythereum.
You need to hack it using npm-shrinkwrap and lock all your dependencies on specified versions. (Which is not usable for libraries.)
Also the package author recommends to not use node-scrypt:
Sorry guys, I was having a bit of trouble updating things. I do intend to publish soon though.
Quick question for anyone out there: I was under the impression that Node provides Scrypt encryption in it's own core libraries. If so, why are people still using this?
Are there any plans to remove or replace this dependency?
Thanks!
The text was updated successfully, but these errors were encountered:
The packge depends on "node-scrypt" package which is deprecated:
The package fails to build in last released version and it prevents to
npm install
projects having that or THIS package in dependencies:web3/web3.js#3408 (comment)
(I had the same build issue on Fedora Linux in app with keythereum dependency - the scrypt was failing to build.)
The fix for this is merged, but the package maintainer is unable to release fixed version:
barrysteyn/node-scrypt#197 (comment)
The only solution is to use version from git:
But that is pretty complicated if your package depends indirectly, like through keythereum.
You need to hack it using npm-shrinkwrap and lock all your dependencies on specified versions. (Which is not usable for libraries.)
Also the package author recommends to not use node-scrypt:
Are there any plans to remove or replace this dependency?
Thanks!
The text was updated successfully, but these errors were encountered: