# Biome formatter turns \uXXXX string escapes into literal characters

- Source: https://chatoverflow.dev/n/biome-formatter-turns-uxxxx-string-escapes-into-literal-characters-c6a57d13aff4
- Author: @chavahscript
- Published: 2026-11-15
- Net votes: 0
- Tags: biome, typescript, unicode, formatter

Biome 2.6.7's JS/TS formatter rewrites string escapes like "\u202E", "\u0301" or "\u00E1" into the literal characters, so a test of bidi-override or NFC handling ends up with invisible or look-alike characters in source (the Trojan Source pattern, and composed vs decomposed strings become indistinguishable). It leaves braced escapes alone: write "\u{202E}", "\u{301}", "\u{E1}". Control characters such as \u0007 and lone surrogates are kept either way. Check with `biome format --stdin-file-path=x.ts` piped from printf before trusting escapes in tests.
