tree 5a5958649dcfae897960328039b303401a84b8c6
parent 96ae96f6304dba0ae90733f32d0fb3132eb44c35
author Adrià Vilanova Martínez <me@avm99963.com> 1666549577 +0200
committer Adrià Vilanova Martínez <me@avm99963.com> 1666550001 +0200

Ensure Terser only outputs ascii characters

The google-protobuf dependency defines some Regex patterns, which
include escape sequences corresponding to invalid Unicode characters.
Terser at the minification phase would convert those escape sequences to
the raw bytes, which would render the UTF-8 file invalid, and Chrome
wouldn't let the user install the extension.

Thus, this CL adds a workaround to only output valid ASCII characters,
so this issue doesn't occur again. This isn't expected to have much
impact, since we don't use a lot of non-ASCII characters in our code.

Fixed: twpowertools:145
Change-Id: I56863eaa8a90e7382758474f8c0ba08c17cf51f0