fix: handle v-for with v-once correctly

vuejs · Sep 9, 2024 · 9441b3a · 9441b3a
1 parent 904167f
commit 9441b3a
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 1 deletion.
diff --git a/packages/language-core/lib/codegen/template/vFor.ts b/packages/language-core/lib/codegen/template/vFor.ts
@@ -51,7 +51,8 @@ export function* generateVFor(
 		ctx.addLocalVariable(varName);
 	}
 	let isFragment = true;
-	for (const argument of node.codegenNode?.children.arguments ?? []) {
+	// children is undefined with v-once (#4827)
+	for (const argument of node.codegenNode?.children?.arguments ?? []) {
 		if (
 			argument.type === CompilerDOM.NodeTypes.JS_FUNCTION_EXPRESSION
 			&& argument.returns?.type === CompilerDOM.NodeTypes.VNODE_CALL

diff --git a/test-workspace/tsc/passedFixtures/vue3/#4827/main.vue b/test-workspace/tsc/passedFixtures/vue3/#4827/main.vue
@@ -0,0 +1,3 @@
+<template>
+	<pre v-for="_ in []" v-once></pre>
+</template>