fix: use fragment end anchor as vfor anchor

diff --git a/packages/runtime-vapor/src/apiCreateFor.ts b/packages/runtime-vapor/src/apiCreateFor.ts
index 240c85fb90e195728a0808c5ad05c3c227693dd5..3104f4b030aadba4024918f14f19c6f26f78d8c3 100644 (file)
--- a/packages/runtime-vapor/src/apiCreateFor.ts
+++ b/packages/runtime-vapor/src/apiCreateFor.ts
@@ -98,10 +98,10 @@ export const createFor = (
   let currentKey: any
   let parentAnchor: Node
   if (isHydrating) {
-    parentAnchor = locateVaporFragmentAnchor(
-      currentHydrationNode!,
-      FOR_ANCHOR_LABEL,
-    )!
+    parentAnchor =
+      locateVaporFragmentAnchor(currentHydrationNode!, FOR_ANCHOR_LABEL) ||
+      // fallback to the fragment end anchor if in ssr slots vnode fallback
+      locateVaporFragmentAnchor(currentHydrationNode!, ']')!
     if (__DEV__ && !parentAnchor) {
       // this should not happen
       throw new Error(`v-for fragment anchor node was not found.`)