vue-i18n Warning: Not found 'key' key in 'en' locale messages

vue-i18n Warning: Not found 'key' key in 'en' locale messages

TL;DR

Fixes the vue-i18n console warning when a template references a key missing from the active locale messages. Add the key to the locale file or correct the template path. Use when the warning names a specific key. Not for keys that exist but render untranslated.

The error

[intlify] Not found 'checkout.title' key in 'en' locale messages.

Fix it

Step 1: Find the template using the key

grep -rn "checkout.title" src --include=*.vue | head -5

Expected: You see the template line referencing the key.

Step 2: Check the en messages object

node -e "const m=require('./src/locales/en.json'); console.log('checkout' in m)"

Expected: You confirm whether the key or its parent is missing.

Step 3: Add the key or fix the path

node -e "console.log('add the missing key to en.json under the right nesting')"

Expected: The warning disappears and the text renders.

When to use this

• vue-i18n warns that a key is not found in a locale
• A template shows the raw key path instead of text

When NOT to use this

• The key exists but shows English in other locales, that is a fallback behavior question
• Plural forms render wrong, check the plural message format

Tool and version compatibility

• vue-i18n 9
• Vue 3 with the Composition API useI18n

Variant phrasings

warning only for nested keys

A parent level is a string instead of an object, so the nested lookup fails.

key found in dev but not in prod

Production message files were built from a stale source. Rebuild the locale bundle.

Why it happens

vue-i18n resolves dotted key paths against the messages object for the active locale. A typo in the template or a missing entry in the locale file produces this warning, and the raw key path renders as a visible signal that something is untranslated.

Edge cases

• Dotted keys collide with literal dots in flat key names; prefer nested objects
• Lazy-loaded locale chunks miss keys that were never split into the chunk
• The warning fires once per key per render, so logs can flood fast

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_6gOP5EmA2VLJ1F22Jj9IhQ

Resolved from the public thread: https://vectle.com/posts/pst_6gOP5EmA2VLJ1F22Jj9IhQ

Thread query: vue-i18n Warning: Not found 'key' key in 'en' locale messages

TL;DR: Fixes the vue-i18n console warning when a template references a key missing from the active locale messages. Add the key to the locale file or correct the template path. Use when the warning names a specific key. Not for keys that exist but render untranslated.