Emojis work properly but sometimes they don't. #9289

Closed
opened 2026-01-31 01:50:49 +00:00 by claunia · 13 comments
Owner

Originally created by @w3dg on GitHub (Jun 26, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.418]
Windows Terminal version : 1.0.1401.0

Git Bash might not really be tied to only this.

Steps to reproduce

Have a javascript file which console.logs emojis and some text. run that thru node or do a yarn install with --emoji true flag.

Expected behavior

To display emojis perfectly alright

Actual behavior

It works for some emojis and not always but if cat or type is run then it shows emojis perfectly.


The sparkles emoji is fine but the others are not

As you can see, in node it doesnt work. but while catting it it does work and the check mark and some others are the only that works

Originally created by @w3dg on GitHub (Jun 26, 2020). # Environment ```none Windows build number: Microsoft Windows [Version 10.0.18362.418] Windows Terminal version : 1.0.1401.0 Git Bash might not really be tied to only this. ``` # Steps to reproduce Have a javascript file which console.logs emojis and some text. run that thru node or do a `yarn install` with `--emoji true` flag. # Expected behavior To display emojis perfectly alright # Actual behavior It works for some emojis and not always but if `cat` or `type` is run then it shows emojis perfectly. ![](https://i.imgur.com/TtLtpx7.png) The sparkles emoji is fine but the others are not ![](https://i.imgur.com/7HV9nn8.jpeg) As you can see, in node it doesnt work. but while catting it it does work and the check mark and some others are the only that works
claunia added the Resolution-ExternalNeeds-Tag-Fix labels 2026-01-31 01:50:49 +00:00
Author
Owner

@w3dg commented on GitHub (Jun 26, 2020):

I just tested the same on Hyper Terminal and can say that the issues with yarn occurs there as well and in a same way, the single width characters such as ✅ or ✨ show up correctly.

@w3dg commented on GitHub (Jun 26, 2020): I just tested the same on Hyper Terminal and can say that the issues with yarn occurs there as well and in a same way, the single width characters such as ✅ or ✨ show up correctly.
Author
Owner

@w3dg commented on GitHub (Jun 26, 2020):

An update, i had a screen recording for a video dated in Apr 2 2020, in which i used a tool called Vercel to deploy my website. Their CLI just like yarn used emojis and the emojis worked fine although the check mark was small.

But in my version now, only the checkmark shows up not the other ones.

@w3dg commented on GitHub (Jun 26, 2020): An update, i had a screen recording for a video dated in Apr 2 2020, in which i used a tool called Vercel to deploy my website. Their CLI just like yarn used emojis and the emojis worked fine although the check mark was small. ![](https://cdn.discordapp.com/attachments/704635164386525235/726058206580965436/unknown.png) But in my version now, only the checkmark shows up not the other ones. ![](https://cdn.discordapp.com/attachments/704635164386525235/726058660437950555/unknown.png)
Author
Owner

@DHowett commented on GitHub (Jun 26, 2020):

If you copy/paste those characters into a text editor, do they come back out as Emoji?

@DHowett commented on GitHub (Jun 26, 2020): If you copy/paste those <?> characters into a text editor, do they come back out as Emoji?
Author
Owner

@DHowett commented on GitHub (Jun 26, 2020):

Debugging: the character coming out of node has already been replaced with U+FFFD. It's been corrupted before the console subsystem even gets it.

They must have changed something that made them even worse console citizens than they already were.

@DHowett commented on GitHub (Jun 26, 2020): Debugging: _the character coming out of node has already been replaced with U+FFFD_. It's been corrupted before the console subsystem even gets it. They must have changed something that made them even worse console citizens than they already were.
Author
Owner

@w3dg commented on GitHub (Jun 27, 2020):

1

If you copy/paste those characters into a text editor, do they come back out as Emoji?

If i just copy and paste, they still remain the same characters.

2

If i put the output to a file while in node, it works fine and are emojis.

image

And this is more interesting

image

maybe it is infering when to use emojis if it is in console or not.

@w3dg commented on GitHub (Jun 27, 2020): #### 1 > If you copy/paste those <?> characters into a text editor, do they come back out as Emoji? If i just copy and paste, they still remain the same <?> characters. #### 2 If i put the output to a file while in node, it works fine and are emojis. ![image](https://user-images.githubusercontent.com/51162936/85913801-61c12400-b855-11ea-960e-56dadf229bd1.png) And this is more interesting ![image](https://user-images.githubusercontent.com/51162936/85913865-1ce9bd00-b856-11ea-9b2f-de4c204ffb87.png) maybe it is infering when to use emojis if it is in console or not.
Author
Owner

@w3dg commented on GitHub (Jun 27, 2020):

This condition checks for the os and the platform/terminal
ac21dbf16a/src/cli/index.js (L112)

So yarn kinda will not bother much. But the thing still will persist with Vercel as they render emojis whatsoever and also with a tool called now-config which prints emojis whatsoever

@w3dg commented on GitHub (Jun 27, 2020): This condition checks for the os and the platform/terminal https://github.com/yarnpkg/yarn/blob/ac21dbf16a5d2d5f4cb032f5da5313949db3fb71/src/cli/index.js#L112 So yarn kinda will not bother much. But the thing still will persist with Vercel as they render emojis whatsoever and also with a tool called [now-config](https://www.npmjs.com/package/now-config) which prints emojis whatsoever
Author
Owner

@w3dg commented on GitHub (Jun 29, 2020):

hey @DHowett any updates / investigations / thoughts about this issue?

@w3dg commented on GitHub (Jun 29, 2020): hey @DHowett any updates / investigations / thoughts about this issue?
Author
Owner

@DHowett commented on GitHub (Jul 10, 2020):

Unfortunately, all I can find here is applications or runtimes that are failing to pass the emoji through.

Node for Windows refuses to send the emoji correctly. Evidence: node under WSL works fine, with the same javascript file. ☹️

image

@DHowett commented on GitHub (Jul 10, 2020): Unfortunately, all I can find here is applications or runtimes that are failing to pass the emoji through. Node for Windows refuses to send the emoji correctly. Evidence: node under WSL works fine, with the same javascript file. ☹️ ![image](https://user-images.githubusercontent.com/189190/87106419-43bed080-c212-11ea-9b2d-7bc5a2618bea.png)
Author
Owner

@DHowett commented on GitHub (Jul 10, 2020):

I've gotta resolve this one as external. If we go make enough noise over on the Node repo, perhaps they'll listen.

@DHowett commented on GitHub (Jul 10, 2020): I've gotta resolve this one as external. If we go make enough noise over on the Node repo, perhaps they'll listen.
Author
Owner

@DHowett commented on GitHub (Jul 10, 2020):

Some more info here; 086482da6d

@DHowett commented on GitHub (Jul 10, 2020): Some more info here; https://github.com/nodejs/node/commit/086482da6dc50693c72a25a64774103e6c1a5e1a
Author
Owner

@DHowett commented on GitHub (Jul 10, 2020):

And here is the code where they make an incorrect assertion about our Unicode support.

1198aebd2d/deps/uv/src/win/tty.c (L2124-L2129)

@DHowett commented on GitHub (Jul 10, 2020): And here is the code where they make an incorrect assertion about our Unicode support. https://github.com/nodejs/node/blob/1198aebd2db710b22bfed003edcf8cca2db8a174/deps/uv/src/win/tty.c#L2124-L2129
Author
Owner

@DHowett commented on GitHub (Jul 10, 2020):

/dup https://github.com/libuv/libuv/issues/2909

@DHowett commented on GitHub (Jul 10, 2020): /dup https://github.com/libuv/libuv/issues/2909
Author
Owner

@ghost commented on GitHub (Jul 10, 2020):

Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!

@ghost commented on GitHub (Jul 10, 2020): Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#9289