-
Notifications
You must be signed in to change notification settings - Fork 26
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
Scrypt dependency is no longer maintained and fails on node12 #34
Comments
These look like the downstream dependencies:
|
Is this same error blocking from installing the npm package in the first place? Getting a similar error when trying to install for the first time: $ sudo npm install -g @dappnode/dappnodesdk
Error: Error: Command failed: ./configure /usr/local/bin/dappnodesdk -> /usr/local/lib/node_modules/@dappnode/dappnodesdk/src/dappnodesdk.js
gyp ERR! configure error npm ERR! A complete log of this run can be found in: |
I was able to install dappnode on node:11 if I removed the |
@Leibniz137 @Blockchainbrett Is this still an issue? Maybe within these 6 months the libraries were updated to be suitable for Node 12, I just tried and compiled without issues on a Linux Mint with NodeJS v12.15.0. |
@Leibniz137 @Blockchainbrett I've experienced your issue while trying to install the dappnodesdk in a remote server. Installing locally in a dummy project fixed the issue. After some tests I can confirm that packages (or its dependencies) that need a Right now the only dappnodesdk dependency that requires a build is |
I've been able to reproduce the issue and fix it with this PR #64. It will be released soon as a new version. Feel free to try it them and let us know if it fixes your issues |
I upgraded to node 13.8.0 and ran |
gotta love the npm ecosystem
fails on node version
12.4.0
compilation errors
scrypt.js
It appears the error is coming from scrypt, which is a nested dependency of the sdk:
this appears to be a similar issue with the same root cause: syscoin/sysethereum-contracts#1
The text was updated successfully, but these errors were encountered: