-
Notifications
You must be signed in to change notification settings - Fork 287
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
Windows electron #435
Windows electron #435
Conversation
This is working well on windows 10 w/ https://github.com/joshuef/safe-nodejs in the safe browser 🎉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is exciting! I learned some cool techniques from the PR too, like using xvfb and spectron to test Electron apps in CI. 👍
I left a few questions inline. And a few more:
- Does this need any changes to the Electron guide?
- What were your thoughts on the whole question of an
--electron
flag versus trying to automatically work both inside and outside Electron? - What were your thoughts on eliminating the need for
electron-build-env
? Still worth investigating but not part of this PR?
No changes necessary.
I don't think adding a flag is necessary. The only difference is linking win delay. The
I think it's worth investigating as a separate PR. |
I think if it "almost always" works, we can experiment with just doing this by default and learning where, if anywhere, it breaks. Once we can characterize that we can think about e.g. how to maybe create an opt-out flag. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Total side note, but for testing electron apps, I'd hiiighly recommend testcafe over spectron. I've found it to be wayyyy more stable and easier to use too! |
Hello @kjvalencik , great to hear you fixed some issues on Windows and Linux. we are experiencing some of those issues (#394). any plans when you want to include these fixes in a neon release? |
@marcmo Yes, they all need to be inline. We are in the process of merging a fairly large PR that is the prep work for N-API. I will cut a release later this week after that lands. Thanks for your patience! |
Hello @kjvalencik Glad to hear that you will publish this release. I'm waiting for this release so eagerly!:smile: |
Fixes #399
Fixes #389
Fixes #394
Fixes #194
Replaces #404