Fixed issue where useQuery() would not correctly trigger a new execution when the query or parameters changed while using StrictMode.

Author: Chriztiaan

.changeset/heavy-coats-serve.md

@@ -0,0 +1,5 @@
+---
+'@powersync/react': patch
+---
+
+Fixed issue where `useQuery()` would not correctly trigger a new execution when the query or parameters changed while using StrictMode.

packages/react/src/hooks/watched/useWatchedQuery.ts

@@ -16,6 +16,11 @@ export const useWatchedQuery = <RowType = unknown>(
 ): QueryResult<RowType> | ReadonlyQueryResult<RowType> => {
   const { query, powerSync, queryChanged, options: hookOptions, active } = options;
 
+  const queryChangeRef = React.useRef(false);
+  if (queryChanged && !queryChangeRef.current) {
+    queryChangeRef.current = true;
+  }
+
   function createWatchedQuery() {
     if (!active) {
       return null;
@@ -44,14 +49,15 @@ export const useWatchedQuery = <RowType = unknown>(
   // Indicates that the query will be re-fetched due to a change in the query.
   // Used when `isFetching` hasn't been set to true yet due to React execution.
   React.useEffect(() => {
-    if (queryChanged) {
+    if (queryChangeRef.current) {
       watchedQuery?.updateSettings({
         query,
         throttleMs: hookOptions.throttleMs,
         reportFetching: hookOptions.reportFetching
       });
+      queryChangeRef.current = false;
     }
-  }, [queryChanged]);
+  }, [queryChangeRef.current]);
 
   return useNullableWatchedQuerySubscription(watchedQuery);
 };