-
Notifications
You must be signed in to change notification settings - Fork 19
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
Error with build, missing binary? #6
Comments
Hi, sorry for the delay, I didn't receive any notification from github about this issue 🤔. I need more information to understand what is going wrong here... |
Here is the output from npm install - sanitized a little for folder names, etc. Maybe you can see what is going wrong... I'm running this on MacOS 10.13.6 , npm version 6.13.6
|
I just attempted to clone and build on Mac OS 10.14.6, npm 6.11.3, node v12.12.0, and ran into similar npm install issues. Seems like a great tool any help getting it up and running would be much appreciated. |
Hi, the problem is related to fsevents as you can see here: The solution is to use the latest version of fsevents, you can do this by cloning the repo, add this dependency in the package.json
and then run
An alternative is to clone the repo and run the following commands sequentially:
This should solve the issue, let me know if it's all ok. |
Thanks @ulver2812, that got me a little closer. Npm install still failed for me after the fsevents update, and it seemed to be related to an old version node-gyp that was requested by angular-devkit/build-angular. I unpinned the angular-devkit/build angular to pull the latest version, reinstalled all the dependencies, and that worked without throwing errors. However, when I tried
I got different errors, seemingly related to angular-cli:
|
Hi @nathanielrindlaub , I have tried the solution posted above on:
Following those steps:
And didn't get any error, can you confirm that you have followed the above steps in a newly cloned repo ? |
I followed the above steps, and it is working for me now. Thank you! npm 6.13.6 Not sure if I should close this issue/question since you have another customer still pending? |
@johnpetersjr , it's better to wait the @nathanielrindlaub response. If it's all ok I can commit a fix and close the issue. |
Hey @ulver2812 - followed your steps and got the following error on the last npm install step:
I think the issue maybe occurs when you're trying to run later versions of node (I'm on 12.12.0 and it appears you guys are on 10.x and 11.x). If you upgrade node, does the npm install still work for you? |
@nathanielrindlaub , I'm sorry but I can't try to use different version of node now. Similar issue here: nodejs/node-gyp#1941 I'm pretty sure that there's an incompatibility with node 12, unfortunately I'm to busy now, I can't update the project, but the solution to build the app on your own is pretty easy, use nvm to switch temporarily on node 11. Let me know if it works so I can close the issue, thanks. |
Tried to download and install this today, got this error message:
Error output:
node-pre-gyp WARN Using request for node-pre-gyp https download
node-pre-gyp WARN Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.2.7/fse-v1.2.7-electron-v2.0-darwin-x64.tar.gz
node-pre-gyp WARN Pre-built binaries not found for [email protected] and [email protected] (electron-v2.0 ABI, unknown) (falling back to source compile with node-gyp)
node-pre-gyp WARN Pre-built binaries not installable for [email protected] and [email protected] (electron-v2.0 ABI, unknown) (falling back to source compile with node-gyp)
node-pre-gyp WARN Hit error Connection closed while downloading tarball file
rm: ./Release/.deps/Release/obj.target/fse/fsevents.o.d.raw: No such file or directory
make: *** [Release/obj.target/fse/fsevents.o] Error 1
gyp ERR! build error
I'm guessing some binary is missing from S3?
The text was updated successfully, but these errors were encountered: