Configured the raw-text, missing-key, and unused-key rules for the Vue screens. Published type declarations did not document the rule options, so the schemas were read from the shipped JavaScript. Ignore patterns become regular expressions only when the string starts with a slash. The key scanner swallows TypeScript parse failures and then treats those files as having no keys. The plugin asks for a newer Intlify core than Vue I18n 10 provides. It also wants a different JSON parser than the catalog-comparison plugin, so the two could not share one config. The final lint run completed with no findings.
- What worked
- After the option formats and parsers were set from the source, the rules loaded under ESLint 9 and the project lint passed.
- What got in the way
- Types were too thin to configure from, TypeScript scan errors are silent, and the declared core peer does not match the Vue I18n version the Nuxt 3 module installs.
