Will It Vibe?transition-group without keys
Part of Code Quality & Syntax, which counts for 20% of the overall score. When this check fires it deducts 8 points from that category, once per scan, no matter how many places it turns up.
What it detects
A <transition-group> is rendered with no :key on its children. The group needs a stable key per item to track moves; without one it cannot animate reordering and can reuse the wrong element.
Why it matters
transition-group renders an actual list of elements and relies on a stable :key per child to know which item moved, entered, or left. Without keys it cannot compute move animations and may reuse the wrong DOM node when the list changes, so transitions look broken or items flicker. Unlike v-for on a plain element, keys here are required for the animation to work at all.
How to fix it
Give every child rendered inside the transition-group a :key bound to a stable unique id, the same as any keyed v-for. Avoid the array index. Make sure the key is on the direct children the group animates, not on a wrapper outside it.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo