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

Update Electron to v6 #3785

Merged
merged 54 commits into from Oct 10, 2019
Merged

Update Electron to v6 #3785

merged 54 commits into from Oct 10, 2019

Conversation

razfriman
Copy link
Contributor

Update to Electron 6.0.0.

Update packages:

  • electron
  • electron-builder
  • electron-rebuild

Update the nodeIntegration default which was changed in Electron 5.0.0.

Add missing plist package required from updating the packages

@razfriman
Copy link
Contributor Author

Anyone able to help me figure out why the CI is failing. I don't seem to be getting all of these warnings and errors when I build the app locally

@Stanzilla
Copy link
Collaborator

You need to update node-pty. the old version does not work with node 10+ afaik

@Stanzilla
Copy link
Collaborator

Hey @razfriman are you willing to pick this up again?

@Stanzilla
Copy link
Collaborator

@razfriman
Copy link
Contributor Author

I seem to be having issues doing this upgrade actually. Things don't seem to be working well for me with node 12 and electron 6. Perhaps someone else can take this over

package.json Outdated
"eslint": "4.7.2",
"eslint-config-prettier": "2.6.0",
"eslint-plugin-prettier": "2.3.1",
"eslint-plugin-react": "7.3.0",
"husky": "0.14.3",
"inquirer": "5.1.0",
"node-gyp": "3.6.2",
"node-gyp": "5.0.3",
"node-pty": "^0.8.1",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Stanzilla this is the problem, you need to get on one of the newer beta builds for Electron 6 support. Try node-pty@0.9.0-beta26

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Tyriar hrm, still errors :(

@Stanzilla Stanzilla changed the base branch from master to canary September 11, 2019 15:47
@Tyriar
Copy link
Contributor

Tyriar commented Sep 11, 2019

@Stanzilla You might need to also tweak the version of node you're building with. @deepak1556 what version of node.js should builds be using with Electron 6?

@Stanzilla
Copy link
Collaborator

C:\projects\hyper\app\node_modules\node-pty>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "" rebuild ) 
gyp info it worked if it ends with ok
gyp info using node-gyp@3.8.0

it seems to be using an old version of node-gyp, not sure why

@Stanzilla
Copy link
Collaborator

@Stanzilla You might need to also tweak the version of node you're building with. @deepak1556 what version of node.js should builds be using with Electron 6?

https://electronjs.org/blog/electron-6-0 says 12.4.0, CI seems to use gyp info using node@12.6.0 | win32 | x64 so should be fine?

@deepak1556
Copy link

deepak1556 commented Sep 11, 2019

@Stanzilla electron@6.0.8 will break native module compilation on windows due to electron/electron#20185, it has been fixed yesterday and new version will be released today, please update to that when its available. It should fix the build issues you are seeing.

@Stanzilla
Copy link
Collaborator

@deepak1556 oh interesting, thanks! I hope this really is it then, because I tried with 6.0.0 before and it was the same issue

@Stanzilla Stanzilla added the 🎨 Type: Enhancement Issue or PR is an enhancement request/proposal for Hyper label Oct 10, 2019
@ivanwonder
Copy link
Contributor

oh, missed it. wait for the feedback of @LabhanshAgrawal about the initial load resize issue.

@Stanzilla
Copy link
Collaborator

yup!

@LabhanshAgrawal
Copy link
Collaborator

LabhanshAgrawal commented Oct 10, 2019

The initial load resize is working. I can see it being rendered a bit small and then resizing but it's very quick and isn't really a problem according to me.
The text rendering thing is still there though.

@Stanzilla
Copy link
Collaborator

@LabhanshAgrawal can you make a screenshot/video of that remaining problem, please?

@ivanwonder
Copy link
Contributor

I think the text rendering is the problem of fonts or browser. https://stackblitz.com/edit/typescript-dausj9?file=index.ts you can test with different fonts.

@LabhanshAgrawal
Copy link
Collaborator

@Stanzilla
Screenshot 2019-10-10 at 19 22 08

@Stanzilla
Copy link
Collaborator

Oh yeah, I'd probably blame that on fonts

@LabhanshAgrawal
Copy link
Collaborator

@ivanwonder in this I haven't changed anything, the text looks moved up to me. Is this supposed to be like this?
Screenshot 2019-10-10 at 19 23 28

@LabhanshAgrawal
Copy link
Collaborator

Ok I tried with my terminal fonts. Maybe the issue is really with the fonts. If you're not facing any problem then you should ignore this as it might be an issue with my patched fonts.
Screenshot 2019-10-10 at 19 31 58

@ivanwonder
Copy link
Contributor

Look the alphabet j, it's in the middle.

@LabhanshAgrawal
Copy link
Collaborator

yep, seems like my powerline glyphs are buggy

@ivanwonder
Copy link
Contributor

if you mind this, try render type dom. it shows ok.

@LabhanshAgrawal
Copy link
Collaborator

it's ok, I'll look for new fonts

@ivanwonder
Copy link
Contributor

if #3848 has been solved. maybe close.

@Stanzilla
Copy link
Collaborator

I will once we merge this one.

@LabhanshAgrawal
Copy link
Collaborator

@ivanwonder I tried out DejaVu Sans Mono for Powerline still have that gap at bottom.
I don't have any issue with 3.0.2 so it shouldn't be a font issue .

@Stanzilla
Copy link
Collaborator

@LabhanshAgrawal but that was before the electron update, caused by the xterm update, right? so not blocking this PR.

@LabhanshAgrawal
Copy link
Collaborator

Checked with canary, no font issue there also

@Stanzilla
Copy link
Collaborator

That does not answer my question though :D

@LabhanshAgrawal
Copy link
Collaborator

I noticed it in xterm update, but it was working on using canvas renderer. But it's not working with this PR even with canvas renderer.

@Stanzilla
Copy link
Collaborator

ok

@LabhanshAgrawal
Copy link
Collaborator

But I think the issue is small, so it should not block the PR, we can track it separately.

@Stanzilla
Copy link
Collaborator

yeah, agree

@LabhanshAgrawal
Copy link
Collaborator

there's nothing else blocking this, right?

@Stanzilla
Copy link
Collaborator

nope I just some last testing and everything looks good, so, merging!

@Stanzilla Stanzilla merged commit 6039acd into vercel:canary Oct 10, 2019
@ivanwonder
Copy link
Contributor

ivanwonder commented Oct 10, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🎨 Type: Enhancement Issue or PR is an enhancement request/proposal for Hyper
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants