Trojan Source Attack checks

[kevmodrome]

Describe the problem

I just discovered this and it looks like a potential attack vector.

A TLDR is something along the lines of using unicode characters to reorder source tokens enabling the attacker to "say" one thing but execute something else. More here: https://www.trojansource.codes

Selected the highest priority importance, not entirely sure that one makes sense though :shrug

Describe the proposed solution

Quoting the Trojan Codes website:

Compilers, interpreters, and build pipelines supporting Unicode should throw errors or warnings for unterminated bidirectional control characters in comments or string literals, and for identifiers with mixed-script confusable characters.

Alternatives considered

I am not 100% this is an issue, maybe someone more knowledgable can chime in?

Importance

i cannot use svelte without it