-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
git clone
web3.js and install fails on >= Node 13.5
#3473
Comments
@cokia This seems like it might be something to report to ganache-cli. Was able to install Web3 as a stand alone package on Mac OSX successfully on Node
Are you able to install Web3 on it's own? |
but when i install ganache-cli standalone, it is possible to install stand alone package... |
Sorry, could you clarify what you mean here? |
When I do 'npm i ganache-cli', the installation works well. I think this is a dependency problem. |
@cokia Ah! You're saying that it's only when ganache-cli sits in a dependency tree with lots of other packages that the installation fails. (We saw the same failure for Node 13 here while experimenting with Github Actions in #3468 yesterday.) However, I was just able to install web3 and ganache-cli together on Node 13.13.0 locally if they were the only two deps... Could you show your package.json for the project you're seeing this error in? That way we can compare it with Web3's own package.json and isolate the cause a little more easily. |
This is the issue that occurred when I did the fork and clone and do the npm i. I don't think it's different from web3 origin package.json.
|
@cokia Ok I finally understand this, sorry and thank you for reporting. |
git clone
web3.js and install fails on >= Node 13.5
Thank you for your contribution. |
Expected behavior
install package successfully
Actual behavior
It makes error
Steps to reproduce the behavior
git clone and just
npm i
itLogs
2020-04-15T05_41_29_873Z-debug.log
Versions
OSX 10.15.2 / Node v13.5.0 / NPM v6.13.4
The text was updated successfully, but these errors were encountered: