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
1 file changed
tree: 5a5958649dcfae897960328039b303401a84b8c6
  1. .github/
  2. cws/
  3. docs/
  4. playbooks/
  5. roles/
  6. src/
  7. templates/
  8. tools/
  9. .clang-format
  10. .editorconfig
  11. .gitignore
  12. .gitreview
  13. .zuul.yaml
  14. i18n-config.toml
  16. Makefile
  17. OWNERS
  18. package-lock.json
  19. package.json
  20. README.md
  21. tagRelease.bash
  22. webpack.config.js

TW Power Tools

Available in the Chrome Web Store

An extension which brings several enhancements to the Google Forums and the Community Console.

For a list of features/enhancements, check out the feature list doc.

Information for contributors

This extension is being actively developed, and everyone is welcome to make feature requests, report issues and contribute code changes.

In order to make feature requests or report issues, please do so at the Monorail Issue Tracker:

To see a more exhaustive guide on how to contribute, and information on how to contribute code changes, please read the following doc:

Beta channel

Before releasing updates to the stable channel, the newest versions are uploaded to the beta channel so they can be tested by everyone who's interested. This is another way to contribute to the project, because beta testing can make us notice bugs before they reach the stable channel.

The beta channel for Chrome is available here.