
Note: This is on a fresh install of Windows 10.
I'm able to see the emojis with yarn (Hyper 3.0.2)

You're getting the ✨ symbol at the end but not other symbols, It might be a fonts issue.
I have fonts configured as fontFamily: '"Source Code Pro", Menlo, "DejaVu Sans Mono", Consolas, "Lucida Console", monospace'
P.S. I am using powershell 6, not cmd. if that might be relevant.
Thanks for replying back. I've tried using different fonts, still no differences. It seems the microsoft emoji font is still working fine when used in browsers:

It seems weird to me why only one emoji font works and the other don't.
Found related issue #3113
I tried again, using your config and the Jetbrains font (also tried with the default config), still faced no issue.
You can try out the latest canary build from here
There's currently a bug in canary with cursorColor and selectionColor, using rgba(), you will have to use hex colors. But you should be able to test the emoji thing easily
Still facing the same issues with vanilla config 😢
Thanks for trying to help though.
Did you try the canary build?
the bugs I mentioned should be fixed soon.
Did you try the canary build?
Yep. Even tried forking the branch and build my own executable. Still the same problem.
I'm out of ideas then 😔.
Yeah I'm having the same issue too, where almost all of the emojis are not showing up on Windows 10 with Hyper Terminal.
I have these plugin's running:
hyperpowerhyper-night-owlThey seem to work everywhere else, but I'm also running Windows Build 19041.84 so it could also be a Windows issue 🤷♂
@mdizo @petercr
We've recently added the xterm unicode plugin, which may fix this
Can you try the latest ci build once and check if it works
@petercr did it work properly for you?
@LabhanshAgrawal Sorry I haven't had a chance to test it out yet. I have been really busy. 😅
I will try it out today, and let you know 👍
@LabhanshAgrawal So I checked out the latest build like you asked. It seemed to work great with oh-my-zsh and a custom Nerd Font. So I am no longer having this issue with the 3.1.0 build 👍