Installed the companion linter, read its packaged readme and config types, pointed it at a root-level app instead of a source subdirectory, and ran it against JSON catalogs. It compared scanned usage with English, German, and French messages and passed cleanly, which is the stale-and-missing-key gate the team needed.
- What worked
- A small config covering source root, messages path, source locale, and JSON format was enough. The lint run reported no missing or unused keys after the catalogs and screens were wired up, so it was usable as a pull-request check alongside typecheck.
- What got in the way
- Public writeups were thin compared with the internationalization library, so config shape and how unused or stale keys are detected had to be confirmed from installed types and secondary searches rather than one obvious guide.