hyper: Run error on Windows 10, branch master.

Everything seemed to be ok when I was still in branch ‘Add windows support’, then I saw the branch had been merged to master, I cloned the app again and built it without any errors, but when I ran the app after npm run pack, I got this error:

Error

Windows 10, branch master, latest code.

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Reactions: 4
  • Comments: 39 (11 by maintainers)

Most upvoted comments

That’s really strange – I can build it without problems here and on AppVeyor. Also, many people can build it as well 😕

I’ll spend some time today or tomorrow on this – I’ll reset my Windows 10 VM and write down every step that I follow to make it work.

Meanwhile: here’s a .exe, a .deb and a .rpm 😄

thanks sugar daddy ^

So, I’m pretty sure this stems from an issue with electron’s custom node runtime and node-gyp’d modules, but I’m not 100% sure. After experiencing the problems listed above I poked and prodded and ended up with a moderately working build after following these steps:

[C:\scratch\hyper]> npm i --save-dev electron-rebuild
[C:\scratch\hyper]> # Added new entry to package.json's scripts:
[C:\scratch\hyper]> # "electron-rebuild": "electron-rebuild -m app/node_modules -w pty.js"
[C:\scratch\hyper]> npm run electron-rebuild
[C:\scratch\hyper]> npm start

This gets me a window that loads, the first tab/shell doesn’t work, but a second one does. I believe that this is most likely due to pty.js issues and may be more easily diagnosed/resolvable than the “unable to build” issues:

image

Error 87:

[C:\scratch\hyper]> net helpmsg 87

The parameter is incorrect.

Running Windows 10 and tested this using node v6.9.1 and v7.1.0, which helps reinforce that it’s related to the electron runtime and compiled/native node modules. It’s not a complete fix, but it has gotten me further than an error and failure to launch every time. I haven’t had more time to play with it, but hopefully this is helpful in some way.

I was able to reproduce 😅 #1001 will fix this if it passes on CI 🙏

hey babe @matheuss were you ever able to reproduce?

Same issue on ubuntu 16.04, @matheuss thanks for the .deb