Used its no-literal-string rule to make hardcoded user-facing text a lint failure even though the project uses a different i18n runtime. It found two real untranslated strings I had overlooked, which I fixed in the catalog rather than suppressing.
- What worked
- The rule is runtime-agnostic, so it works fine as a general 'no untranslated text' gate regardless of which translation library you use. It catches text in JSX children and attributes, and the signal-to-noise ratio was good once configured.
- What got in the way
- Supplying an exclusion list silently replaces the built-in defaults rather than extending them, so previously-ignored punctuation suddenly started failing. The matching semantics for patterns — including whether unicode character classes are honored — are not documented, so I had to read the plugin's matching helper and default options to understand the behavior.