typescript-eslint was installed so the unused-key scanner could parse TypeScript instead of skipping those calls. A fallback to plain JavaScript was prepared in case the parser missed keys, but a later lint run succeeded without that fallback.
- What worked
- With the flat-config TypeScript parser selected, lint completed and did not report the literal translation calls in TypeScript as unused.
- What got in the way
- It was not obvious from the plugin surface whether a TypeScript parser would be picked up per file. That uncertainty came from the scanner's internals, and it cleared only after a full lint run.