-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
install-app-deps fail for fsevents #3555
Comments
I get the same issue when I clone my existing project on a new machine. Digging a bit deeper into the cause, I removed 2 packages Node: v10.14.2
Package.json:
|
Thank you!!! I did as you, remove & reinstall manually, it didn't work at first. Now it even works on the original folder (with "-") and as a bonus it seems likes the binding was done correctly this time
it used the correct configuration node-v64-darwin-x64 |
Following on @PsyGik notes - issue resolved |
@idanwork But I think this is a temporary resolution. Because when I clone the project in another machine, the same issue persists. For now, I've updated the README.md of my project so that future me/other dev won't scratch their hairs out over this. Can you kindly keep this issue open so others can look into this and provide a possible permanent solution? |
I hesitate to reopen this issue since a new version was released, and it may be resolved, I've tried:
seems to work, |
Hi, sadly I think I'm experiencing this error or something related:
my package.json:
|
I got same error as @kkitay So issue should be reopened. |
Dmitry - try switching to yarn. I fixed this by deleting node modules folder and package-lock.json and reinstalling and packing via yarn.
Yarn is strongly recommended over NPM as it turns out.
|
@kkitay thanks, also found that, and yes, yarn works!) |
Hi I've installed using @kkitay 's package.json. I suspect the issue is npm cache/internal fsevents and not related to electron-builder. Attached detailed install log, |
Hi, I got same error. {
"devDependencies": {
"electron": "^4.0.2",
"electron-builder": "^20.38.5",
}
} Errors disappear after restalled dependencies with |
Hi, But as three people already commented the issue is resolved with yarn, it sure smells like npm-cache issue. Attached package-lock as txt |
As mentioned here, #3671 (comment) running
and then building, got me through without errors. It worked for me anyways, without being have to switch to yarn. |
Hi,
I am using chokidar as file monitor for my project, when trying to install the packages on a new machine (or delete the previous package-lock.json)
I get this error in the postinstall script
There are 2 issues here that I don't understand:
I've checked the fs-events-binaries and I believe that there is something wrong with the binding that the builder is trying to download.
It seems that that the download should have been resolved to "v1.2.4/fse-v1.2.4-node-v64-darwin-x64.tar.gz" or similar node-xxx version.
Assuming the package can't be downloaded - it resolves to rebuild it which sounds great but it fails on some different error.
Is this something in my configuration?
This is an example package.json file:
Install log here (too long to post as is)
install output.log
The text was updated successfully, but these errors were encountered: