-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Explore update to Electron 3 #52629
Comments
Issues so far:
|
@bpasero you'll need to re-release https://github.com/bpasero/fsevents in order to pick up nan@2.10.0 |
@Tyriar is that a change compatible with older Electron versions or do we need a specific release only for Electron 3.x? |
@bpasero it's compatible, the latest insiders is using nan@2.10 for node-pty. |
@Tyriar we might have to fork NSFW, I do not think that project is active anymore... |
@Tyriar I published |
We already forked nsfw to vscode-nsfw to release Axosoft/nsfw#47 (repo: https://github.com/Tyriar/nsfw/tree/vscode-release) |
@Tyriar I pushed https://github.com/Microsoft/vscode/tree/electron-3.0.x that compiles. There are some serious issues I have not looked into, e.g. I cannot save files for some reason. |
I believe that one could be due to nodejs/node#2006 |
Saving actually does work, the first time at least. It just doesn't lose the circle indicator and then after that lots of things seem to be broken, like I cannot close the window via custom menu bar and ctrl+r doesn't work to reload. |
@Tyriar can you make a branch on Would be cool to get a build with Electron 3 running for next weeks Electron hackathon ⭐️ . I will start with looking into the weird save issue. |
@rebornix @alexandrudima is this V8 change something we need to change in our code? I remember we once did changes around this where we assume a certain max string length: (via https://v8project.blogspot.com/2017/09/v8-release-62.html) |
Actually this is happening in 58 and 61, it's just way faster: Slow layouts is something we should look out for. I can look into fixing this in xterm.js as this should only be happening when a frame is rendered xtermjs/xterm.js#1606. |
Fyi I got NSFW working now, looks like another change for Node 10 compatibility is needed: https://github.com/bpasero/vscode-nsfw/commit/2c0ff39a2f5157fee04e407014026123e4bd3295 |
We have our first VSCode exploration builds out (see description of the issue for download links). |
It's almost time to start exploring Electron 4 😄 |
Is there somewhere I can get the latest exploration build. I'd like to test out vscode in electron 3.0 |
I don't think so, yet. But you can build it from source How-to-Contribute#build-and-run. |
For real? There are 3 links in the original post with download links to the exploration build, depending on your OS 😳 |
Sorry @dalDevelo , i assumed that @loligans already saw that and is not running on an OS using |
@compilenix. Thanks for clarifying, your response makes sense now. It's perhaps best if @loligans states his exact requirements in his post, to avoid assumptions and...in my case, confusion. Ty |
Yes: #61787 |
Is Electron 3 expected to be ready for the November release or not until February? I'm trying to decide whether to backport a fix in a module I use (which I will do if Electron 3 is Feb+) or just wait for the next release. |
@phv Q1 2019 |
Thanks, I'll backport. Not a big deal. (PS: Improved support for binary dependencies would be welcome and I know you're tracking that elsewhere.) |
Merged to master for our release early February 2019. Should be available in insiders end of week. |
Electron 4 is released, https://electronjs.org/releases#release-notes-for-v400 |
Already builds available: #61787 |
VSCode Exploration Builds with Electron 3.0.x:
The text was updated successfully, but these errors were encountered: