4.0.0-canary.5: Sixel support gets eaten by Windows ConPTY Fallback
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: Windows 11 Pro 25H2
-
Hyper.app version: 4.0.0-canary.5
-
Link of a Gist with the contents of your hyper.json: N/A
-
Relevant information from devtools (CMD+ALT+I on macOS, CTRL+SHIFT+I elsewhere): N/A
-
The issue is reproducible in vanilla Hyper.app: Is Vanilla
Issue
Sixel support gets eaten by the fallback to Windows's old ConPTY. Updating node-pty to 1.1.0 and using useConptyDll:true would utilize the newer version of ConPTY that ships with node-pty 1.1.0 allowing windows users to have sixel support.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the node-pty dependency and the Windows ConPTY fallback configuration, then inspect how useConptyDll is passed for Windows. Update node-pty to 1.1.0 and enable the option so Sixel output is preserved on Windows; verify the behavior in the vanilla Hyper.app setup described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- desktop, operating-systems
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100