packages/compiler-dom/src/transforms/stringifyStatic.ts (1)

217-221: Good early bail for v-once; also bail when v-once appears in descendants.

Current check prevents stringifying the node that directly bears v-once. For robustness, also bail during the subtree walk so a parent isn’t stringified when any descendant has v-once (e.g., nested v-once inside an otherwise eligible wrapper).

Suggested change inside walk():

function walk(node: ElementNode): boolean {
  // Bail if this element (or any visited descendant) has v-once
  if (findDir(node, 'once', true)) {
    return bail()
  }
  const isOptionTag = node.tag === 'option' && node.ns === Namespaces.HTML
  // ...
}

Would you like me to add a focused test covering a nested v-once descendant to ensure we never stringify across it?

packages/compiler-dom/__tests__/transforms/stringifyStatic.spec.ts (1)

529-537: Nice regression test; consider asserting AST shape and add a nested v-once case.

Snapshot is fine, but a small AST-level assertion will more precisely guarantee that only the span group is stringified and the v-once node remains a VNODE_CALL.

Example assertion (inline with this test):

// ensure first child (v-once) stays as VNODE_CALL and second becomes CREATE_STATIC
expect(ast.cached).toMatchObject([
  {
    type: NodeTypes.JS_CACHE_EXPRESSION,
    value: {
      type: NodeTypes.JS_ARRAY_EXPRESSION,
      elements: [
        { codegenNode: { type: NodeTypes.VNODE_CALL } },
        { type: NodeTypes.JS_CALL_EXPRESSION, callee: CREATE_STATIC }
      ]
    }
  }
])

Optionally add a second test for a nested v-once descendant to guard against stringifying a wrapper that contains v-once.

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro