Vue: [Vue warn]: <TransitionGroup> children must be keyed: <li>
Children of <TransitionGroup> lack a unique key, so animations can't track items.
[Vue warn]: <TransitionGroup> children must be keyed: <li>TransitionGroup children must be keyed<transition-group> children must be keyed[Vue warn]: <TransitionGroup> children must be keyed: <div> Meaning
Add :key with a stable unique value to each direct child (not the index if items reorder). v-for inside <TransitionGroup> needs keys; also set tag if you want a wrapper element.
Common causes
v-forwithout:keyinside TransitionGroup- Non-unique/random keys
- Keys on a wrapper instead of direct children
- Conditional children without keys
- Copying
<transition>usage
⚡ Quick fix
<TransitionGroup name="list" tag="ul"><li v-for="i in items" :key="i.id">- Use stable ids
- Put the key on the element directly under the group
Detailed fix by platform
Vue
<TransitionGroup name="fade" tag="ul"><li v-for="t in todos" :key="t.id">{{ t.text }}</li></TransitionGroup>
How to diagnose
- Key — Present?
- Unique — Stable?
- Level — Direct child?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- [Vue warn]: Duplicate keys found during update Vue: [Vue warn]: Duplicate keys found during update: "5", possible duplicate or missing keys
- [Vue warn]: Extraneous non-props attributes Vue: [Vue warn]: Extraneous non-props attributes (class) were passed to component but could not be automatically inherited because component renders fragment or text root nodes
- Duplicate attribute (Vue template) Vue: [plugin:vite:vue] Duplicate attribute. / [vue/no-duplicate-attributes] Duplicate attribute 'class'
Most viewed in Vue
- Property was accessed during render but is not defined Vue: [Vue warn]: Property "x" was accessed during render but is not defined on instance
- Failed to resolve component Vue: [Vue warn]: Failed to resolve component: x
- Avoid mutating a prop directly Vue: [Vue warn]: Avoid mutating a prop directly since the value will be overwritten whenever the parent component re-renders
Other ways to find it
Where this error sits
Origin: On your device. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 5 Nov 2026