-
Notifications
You must be signed in to change notification settings - Fork 201
Install fails because of [email protected] in node 13.2.0 #1419
Comments
I have an even worse message when I install.
npm ERR! A complete log of this run can be found in: |
Hi @vmandal Thanks for reporting. I recommend using an earlier version of node. I currently use node 10. I get the same issue:
|
|
[email protected] must have been defined as a dependency in some package. I found OpenZeppelin / starter-kit also has this dependency I do not know which package is asking for [email protected] while installing OpenZeppelin CLI Is there a work around. |
The recommended workaround is to use an earlier version of node. I currently use node 10. |
We should also support Node 12. I was unable to install the CLI on Node 12 though. Can someone else try and let us know in #1371? |
Updates grpc transitive dependency, which was causing install issues in node 13 Fixes #1419
Updates grpc transitive dependency, which was causing install issues in node 13 Fixes #1419
Hey @vmandal! We have just released 2.7.1 with node 13 support. Please check it out and let us know if it works for you! |
Pre-built binaries not found:
Then fails on building:
|
My bad, I fixed this in 2.7.1, but backported it to |
Ported to 2.8 in 6600961. Will be in the next release candidate. |
404 error here
node-pre-gyp WARN Tried to download(404): https://node-precompiled-binaries.grpc.io/grpc/v1.23.3/node-v79-linux-x64-glibc.tar.gz
node-pre-gyp WARN Pre-built binaries not found for [email protected] and [email protected] (node-v79 ABI, glibc) (falling back to source compile with node-gyp)
so it tries to build it and than it has lot of error
..
many more such errors
The text was updated successfully, but these errors were encountered: