HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
vercel
hyper
TypeScript2016–2025
vercel / hyper · Archived

hyper

A terminal built on web technologies

24Distinct people
26Mentions
0Explicit recommenders
44.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A terminal built on web technologies

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year26 dated mentions

Observed mentions: 2016-07-15 19:54:35 UTC to 2025-03-10 10:30:58 UTC.

02468102016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 9 mentions; 3 submissions, 6 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC936
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC505
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC202
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC413
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC321
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC211
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

What Hacker News says

26 sources
Stack traces are very valuable. Sometimes it can even help to attach them to some object creation, when you later wonder why/how/where this object was created. E.g. in TensorFlow, every single Tensor had a traceback attached to it, so when there was any error later on, it would show you where it was created. This is maybe less needed now with eager mode, but you might have other similar situations. One problem with stack traces is maybe that they can be too verbose. E.g. if you print them for any warning you print to log (or stdout). Sometimes they will be extremely helpful for debugging some problem, but in many cases, you maybe don't need them (you know why you get the warning and/or you don't care about it). You could also add more information to the stack trace such as local variables. That can be even more helpful for debugging then,
Read the rest
but again adds more verbosity. For example, we often use this to add information about relevant local variables: https://github.com/albertz/py_better_exchook One solution to the problem with verbosity is when you have foldable text output. Then the stack trace is folded away (not shown in all details) and you can unfold it to see the details. See the DomTerm demo here: https://github.com/albertz/py_better_exchook#domterm Some more on text folding: https://github.com/PerBothner/DomTerm/issues/54 https://gitlab.com/gnachman/iterm2/-/issues/4950 https://github.com/xtermjs/xterm.js/issues/1875 https://gitlab.freedesktop.org/terminal-wg/specifications/-/... https://github.com/vercel/hyper/issues/1093
In Stack Traces Are Underrated
I have been waiting to try this out for sometime now. I recently tried various terminal emulator tools and I settled on wave terminal. This is a list of these tools for reference. I would list tools that are on both MacOS and Linux which is comparable to this new emulator. But also because I did not try any on windows. - Alacritty (https://github.com/jwilm/alacritty) - waveterminal (https://github.com/wavetermdev/waveterm) - Hyber (https://github.com/zeit/hyper) - Kitty (https://github.com/kovidgoyal/kitty) - Rio (https://github.com/raphamorim/rio) - Tabby (https://github.com/Eugeny/tabby) - Wezterm(https://github.com/wez/wezterm) - Contour (https://contour-terminal.org) - Extraterm (https://github.com/sedwards2009/extraterm) - Warp (https://www.warp.dev/) I didn't like that Warp is VC product as I don't like essential tool like a termina
Read the rest
l in my workflow to be dependent on proprietary VC product.
In Ghostty 1.0
"New Blazing Fast WebGL Engine". Wow really? Major changes - "Emoji support". For fucks sake, seriously? Am I the only one that doesn't want anything of the following _bull shit_? * A terminal emulator that is dependent on an entire web browser (not to mention the layers upon layers of bullshit abstractions all to run something from the 70s). * Support for "emojis" (I mean, come on. It's a _damn terminal_). * To execute code that can hijack control of my shell from any of the 956 dependencies[1] this _heap of shit_ relies on. [1] $ git clone https://github.com/zeit/hyper.git $ cd hyper $ npm install $ ls -lt | wc -l 956
In Hyper 3.0.0
I've been using Hyper 3 Canary for a while, if you're on Windows it's a MASSIVE difference from previous versions - all the normal stuff you expect to work (select to copy, right click paste, rendering, readline shortcuts etc) works (with a little tweaking, see below). It's definitely usable as a daily driver. I've been using Windows Terminal in the last 24 hours and it still has some major bugs. While I'd say Fluent Terminal is the best in terms of being lightweight and feature filled, and Alacritty for raw power if you have big shell workloads, Hyper 3 is pretty damn good and worth a try. Sane defaults: Use pwsh (not cmd, that's the Windows equivalent of launching 70's Bourne shell on a *nix box): shell: "C:\\Program Files\\PowerShell\\6\\pwsh.exe", shellArgs: [], Normal new tab, close window keys, make readline keys work:
Read the rest
keymaps: { "tab:new": "ctrl+t", // Also known as 'close tab' "pane:close": "ctrl+w", // Bug workaround for https://github.com/zeit/hyper/issues/2873 "editor:movePreviousWord": "", "editor:moveNextWord": "" },
In Hyper 3.0.0
The situation for terminal emulators is still bad on Windows. Those web-based ones have no problems with fancy font features like powerline icons or ligatures but they still have a limitation when it comes to color support. [1] Fluent seems to be affected from this as well. The other important feature for me is tmux with mouse support. To my knowledge, only WSLtty [2] does this right. It lacks support for font ligatures but I value a functional tmux more than some ligature eye candy. I still hope that Microsoft will improve their own conhost.exe in further updates. Also, the upcoming 1903 update will improve the color support those web-based terminal emulators. [1] https://github.com/zeit/hyper/issues/1968 [2] https://github.com/mintty/wsltty
In Fluent Terminal – Open-source, native Windows 10 tabbed terminal
My least favorite thing about Hyper was whenever you split a window horizontally you would lose your cursor because it would be hidden "behind" the split pane above it, and then you would have to hit CTRL+C like 20 times or force some output to the screen. I opened an issue for this 2 months ago[0] and the team hasn't responded yet. I'm about ready to call it quits with Hyper (ConEmu has its own set of even worse bugs). The problem with Terminus is it currently has no support for splitting windows, so if you want that behavior you would have to use tmux. Although now with Windows 18.03+ being out, tmux sessions persist after closing your terminal so maybe that's the best way to handle splitting windows. [0]: https://github.com/zeit/hyper/issues/3258
In From macOS to Windows and WSL
I work on the VS Code terminal/xterm.js[1]. Hyper which currently uses a fork of hterm, is in the process of moving over to xterm.js due to the feature/performance improvements we've made over the past 12 months. Hyper's 100% CPU/crash issue[2] for example should be fixed through some clever management of the buffer and minimizing changing the DOM when the viewport will completely change on the next frame. I'd love to see the same set of tests on Hyper after they adopt xterm.js and/or on VS Code's terminal. Related: I'm currently in the process of reducing xterm.js' memory consumption[3] in order to support truecolor without a big memory hit. [1]: https://github.com/sourcelair/xterm.js [2]: https://github.com/zeit/hyper/issues/94 [3]: https://github.com/sourcelair/xterm.js/issues/791
In Terminal and shell performance

Showing the 15 most recent of 26 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.