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
npm install fails on Mac OS X #69
Comments
I have the same issue |
+1 |
I created a pull request to address this: ProjectOpenSea/wyvern-schemas#3 The workaround is to install yarn, though this is an issue with the dependency tree. |
@bcomnes Even after installing yarn, I'm getting the same error. Is there something more to do for your workaround? |
It has to be installed and globally available on your $PATH. Thats the only other caveat I can think of. |
Yep, available globally within $PATH, even from a fresh terminal. Posting the error below if you have any additional insights:
|
Oh you are right. that is a different issue. You are missing a build tool for building a native addon for the package sha3. But sha3 ships a pure JS version now in 2.0. Also it doesnt appear opensea (at least opensea-js@1.1.11) is even relying on sha3 anymore. What does |
At first it was |
Strange. The path that made it look like that package was the issue was this
Looks like its using git cloned dependencies so maybe try clearing your npm cache. |
(Another issue with this package seems to be reliance on non-immutible packages due to its reliance on floating git dependencies... not a good practice if you want reliability). |
I ran this:
Still the same error. I agree with you that not pinning Git dependencies is an issue. |
same issue here |
@jamboj While it's not ideal, according to the You can try running |
I'm running 15 and it works. I'm not sure which build tools I have though. Running an older version might help though if you are having issues. I'm curious where this native version of sha3 is originating though because I'm not seeing it, and it looks like its coming out of a git cloned dependency. |
unfortunately I can't fallback to node 10 as I have another dependency that requires node 14+ |
I ran into the same issue and the only thing that worked for me was to use yarn instead of npm. I did not need to install sha3 and it worked using node v14.16.1 as long as I used yarn. |
What command did you use to install with yarn? |
Are you using node v16+?? I got the same issue using node v16. It works after changed back to v14 LTS |
Was anyone able to get this working? Having the same issues |
First, I set the node version to a v14 version; for instance, v14.17.1 worked for me. Then, I just ran |
Works using node v15 for me, doesn't work with v16. |
This is what it worked for me as well, just using yarn instead of npm and it worked on Node v16.6.2 |
Confirming node v14 worked with NVM. Thank you! |
👍 |
Issue is still present on node v16 though. Any chance of upgrading sha3 lib to solve the issue? |
After further research, it seems like the issue can be fixed by using yarn instead of npm and downgrading to node v14. Looking into fixing this with v16. |
The latest node LTS version is 16, not 14. Are you going to fix this? Should not be closed, since it hasn't been fixed. |
Sorry, didn't mean to close. We are investigating this, but a workaround at the moment is using v14. I will comment on here once I have any updates. |
Using yarn can solve this problem npm install -g yarn |
Mac OS X 10.15.7
node 15.10.0
when trying to install I'm getting the below wall of errors that I can't quite understand.. anyone can help please?
The text was updated successfully, but these errors were encountered: