-
Notifications
You must be signed in to change notification settings - Fork 30
Unable to install Ark-Client on any Node Version (5.x - 8.7.0) #17
Comments
I implemented the populateLedgerAccounts method with async. In case it helps, the versions I'm using are:
|
Have you tried installing the ark-client as it says in the repo ? So the problem is that there are a lot of old mentions to node versions < 7.x (when async was introduced). Now, as mentioned, there are multiple errors, depending on what node version you are running and what repo version:
If you just try and run the latest version of the code and the lastest version of node - such as 8.7.0 - then I get a weird permission denied when using sudo (on Ubuntu) ` sol@z~$ sudo npm install -g arkecosystem/ark-client#master npm ERR! A complete log of this run can be found in: Thanks! |
Sorry @climaxx, I will give this a try soon. I missed your response! |
@climaxx - it worked for me without doing anything special (I am running on Windows with MINGW64) - see below. Can you just run
|
Oh, do you want to post the Log file too? |
Hello, Sorry, I had to get hold of the laptop I was using, in order to have that information. So first of all, I cannot install the ark-client package using npm install - as mentioned previously - I get the same error and you should have seen the logs - some weird permission problem (even if I run as with sudo or change the ownership of the directory that triggers the error). Secondly, if I try to download the zip file and then run npm install (because otherwise it complains about missing dependencies) - I still get a crash - I will attach the file. I am using node version 8.7.0, npm v5.5.1 and Ubuntu 16.04.2 |
@climaxx is it possible to use https instead of git during npm install?
|
Can confirm ... it does not install on new versions anymore. PS C:\Users\Jarunik> node -v CMD output: Complete Log: |
You both seem to have the same errors. It looks to me like a node-hid issue. I'll investigate when I'm on the computer next 🤔 |
@Jarunik - I don't know if it's related but your ark-client-cmd.txt file is showing the below:
You may need to confirm python is installed and in the path specified above. Still looking but if you could fix Python to see if that helped, that would be great! Thanks! |
@climaxx I'm still trying to replicate your issue. Would you mind going to the below link to determine if it resolves the issue for you please: https://docs.npmjs.com/getting-started/fixing-npm-permissions Thanks! |
Updated python and python is installed in that directory. I had ark-client running before. Just broke when i tried to update to the newer version. |
Weird @Jarunik. Your versions aren't vastly different to mine (same major version for node and npm). I wonder if it's a node-hid caching issue (cached on mine), hence why it's not an issue for me. I'll try clearing my cache and trying again |
@climaxx you mention a vagrantfile but there isn't one included with the ark-client. What vagrantfile are you using? |
@Jarunik and @climaxx i'm in the process of setting up a fresh test environment to try to replicate. I have a couple of questions:
|
I don't have the problem anymore with the current state. |
I don't think we're supposed to be using May be worth trying the following: Option 1: Change the permission to npm's default directory
|
To be honest I'm going to close this as no longer an issue for @Jarunik and no reply from @climaxx. Thanks for your suggestions @sleepdefic1t and for confirming @Jarunik. Climaxx can reopen the issue if none of the suggestions help. 👍 |
I have tried to pull previous versions of the ark-client and also use the n utility to switch between node versions.
I have identified at what version this problem occurs (see below).
Also, this happens because before node version 7.6.0 there is no async attribute.
But switching node versions will trigger a HID module core dump.
Also, this happens in the Vagrant file as well - that has Node version 6.9.1 and you cannot install ark-client on that machine.
Last version of Node (8.7.0) with the last version of ark-client has other incompatibilities (which aren't pictured below).
The text was updated successfully, but these errors were encountered: