vercel / vercel/hyper

Reopening hyper after installation throws an error

Open
#3,565 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
44.7k
Forks
3.6k
Avg merge
21m
Merged PRs (30d)
1

Description

  • I am on the latest Hyper.app version
  • I have searched the issues of this repo and believe that this is not a duplicate
  • OS version and name:
  • Hyper.app version:
  • Link of a Gist with the contents of your .hyper.js:
  • Relevant information from devtools (CMD+ALT+I on macOS, CTRL+SHIFT+I elsewhere):
  • The issue is reproducible in vanilla Hyper.app:

Issue

I tried reinstalling and resetting the hyper.js file by removing it, also tried removing remaining contents on registry. I STILL get the same error.
But when I run the installer, it runs smooth, the error will only show everytime I reopen hyper after installation.

What am I missing something here?

Errors:
'A Javascript Error Occured in the main process
Uncaught exception:
Error: connect ENOENT
.\pipe\winpty-conin-12540-1-1d[very long number]
at Object.exports_errnoException(util.js:1024:11)
at exports_exceptionWithHostPort(util.js:1047:20)
at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1150:14)'

'A Javascript Error Occured in the main process
Uncaught exception:
Error: connect ENOENT
.\pipe\winpty-conout-4892-1-1d[very long number]
at Object.exports_errnoException(util.js:1024:11)
at exports_exceptionWithHostPort(util.js:1047:20)
at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1150:14)'

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is identified in the issue. Start by reproducing the failure after installation and use the reported winpty named-pipe ENOENT errors as the starting point; done means Hyper reopens without uncaught main-process errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.