Skip to content
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

Electron 7 beta fails to install #20039

Closed
3 tasks done
mubaidr opened this issue Aug 30, 2019 · 5 comments
Closed
3 tasks done

Electron 7 beta fails to install #20039

mubaidr opened this issue Aug 30, 2019 · 5 comments

Comments

@mubaidr
Copy link

mubaidr commented Aug 30, 2019

Preflight Checklist

  • I have read the Contributing Guidelines for this project.
  • I agree to follow the Code of Conduct that this project adheres to.
  • I have searched the issue tracker for an issue that matches the one I want to file, without success.

Issue Details

  • Electron Version:
    • electron@7.0.0-beta.3
  • Operating System:
    • Windows 10, 18950
  • Last Known Working Electron version:
    • electron@6.0.2

Expected Behavior

electron@7.0.0-beta.3 should install fine.

Actual Behavior

electron@7.0.0-beta.3 fails to install

To Reproduce

Try installing electron@7.0.0-beta.3 on Windows.

Additional Information

npm i -D electron@beta

> electron@7.0.0-beta.3 postinstall D:\Current\temp\node_modules\electron
> node install.js

(node:12560) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, lstat 'C:\Users\username\AppData\Local\Temp\electron-download-fVvnDg\electron-v7.0.0-beta.3-win32-x64.zip'
(node:12560) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:12560) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

+ electron@7.0.0-beta.3
@vladimiry
Copy link

EPERM error on Window is known to happen when there is concurrent and frequent access to the files, even if just access to read operation, see some details here. Means it could be an issue of npm itself doesn't handle properly the EPERM errors on Windows. So try running the command multiple times.

@ckerr
Copy link
Member

ckerr commented Aug 30, 2019

This doesn't appear to be an Electron issue -- several other packages have also hit this when being installed by npm on Windows.

nodejs/node#17080 is an upstream Node issue reported on this, which points to how one user got things working by following the steps described in https://stackoverflow.com/questions/20711240/how-to-completely-remove-node-js-from-windows

I'm going to close this ticket since it doesn't appear to be an Electron issue, but I hope the links above help you in getting things working again!

@ckerr ckerr closed this as completed Aug 30, 2019
@mubaidr
Copy link
Author

mubaidr commented Aug 30, 2019

Since the electron v6 was installing fine on my system, this made think that electron v7 beta installer had issue. But now I beleive installation script has been updated for beta which somehow is effected by the outstanding nodejs issue.

Thanks for the info.

@xielehe
Copy link

xielehe commented Oct 23, 2019

I have the same issue.

@MontyZhao
Copy link

MontyZhao commented Oct 24, 2019

Edited by @groundwater

If you are using "cnpm" instead of "npm" to install the electron, this question is alway appear in version 6.1 - 7.0 .

So, it's easy to resulve the issue. USE "npm".

This mistake had taked off six hours of my life!

/(ㄒoㄒ)/~~

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants