From 773189b4b0d49e2e1c6d1a70cdf88bf416597ac2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Manolo=20Cant=C3=B3n?=
 <59761854+m-canton@users.noreply.github.com>
Date: Sat, 25 Jul 2026 04:55:29 +0200
Subject: [PATCH] Removes await in revalidate uses and sets
 applyResponseMetadata as sync

revalidate function is not async, so it does not need await.
---
 src/data/action.ts | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/data/action.ts b/src/data/action.ts
index 84ffbb13..bf5eb5bd 100644
--- a/src/data/action.ts
+++ b/src/data/action.ts
@@ -423,7 +423,7 @@ export function setupFlightDataConsumer(router: RouterContext) {
  * the flight-data consumer and the action response path (which still sees
  * metadata-bearing responses when no flight data was collected).
  */
-async function applyResponseMetadata(
+function applyResponseMetadata(
   metadata: Response | undefined,
   navigate: Navigator,
   flightData?: Record<string, any>
@@ -446,7 +446,7 @@ async function applyResponseMetadata(
   // set cache
   flightData && Object.keys(flightData).forEach(k => query.set(k, flightData[k]));
   // trigger revalidation
-  await revalidate(keys, false);
+  revalidate(keys, false);
 }
 
 async function handleResponse(
@@ -483,6 +483,6 @@ async function handleResponse(
   // function's unwrapped value. Do not treat that value as a second plain
   // action response and invalidate the freshly seeded query cache again.
   if (!metadataHandled || metadata || flightData)
-    await applyResponseMetadata(metadata, navigate, flightData);
+    applyResponseMetadata(metadata, navigate, flightData);
   return data != null ? { data } : undefined;
 }