Cool usage hint: Invisible prefix

[mark-hahn]

I have developed several vscode extensions that put invisible unicode chars in lines so I can find lines my extension generated. This is the same problem that turbo log solved by using the 🚀prefix. But if you wish you can specify an invisible prefix to remove that ugliness from your logs.

I use the zero-width space \u200B as my prefix. You can copy the char from inside these brackets: [​]. You can verify it is there by using an arrow key to move the cursor over it. It will seem like the arrow key is broken when it doesn't move at that char. Just hold the shift key down while stepping "over" the char to copy it to the clipboard and paste into the prefix setting.

Note: vsCode has a setting to show invisible chars by showing a tiny rectangle. It defaults to true but you can turn off that setting. If you do turn it off be careful not to edit the log line in such a way the the invisible char gets lost in your code. You will get confusing syntax errors. I have used this technique in my extensions with the vsCode setting turned off and I've never had a problem.

Enjoy ...

[mark-hahn]

More on that note: I just realized that since the log output doesn't show the little invisible character rectangle that the editor shows there is no reason to turn off that indicator. And seeing it in the code is a good thing to keep track of the invisible chars. So I recommend making sure the setting Editor › Unicode Highlight: Invisible Characters is turned on. It defaults to on.

[Chakroun-Anas]

Hi @mark-hahn,

Clever workaround — using a zero-width space as a prefix is definitely creative!

We actually experimented with that approach a while back, but many users reported issues with linters, formatters, and code quality tools flagging invisible characters as invalid or even corrupting diffs. Because of that, we reverted to visible prefixes for reliability.

Still, it’s a neat trick for anyone who wants a purely local setup!

[mark-hahn]

users reported issues with linters, formatters, and code quality tools

That is odd. How could \u200B cause a problem when 🚀 doesn't? If the chars were just invisible and not zero-width the display of text would look screwed up which is maybe what caused them to appear to have problems. In any case I'm using \u200B right now on this pr and we'll see if eslint chokes on it. I don't use formatters, or code quality tools.