@trackunit/react-core-contexts-test 1.12.40 → 1.12.42

package/index.cjs2.js

@@ -13490,36 +13490,38 @@ const mockWidgetConfigContext = {
     closeEditMode: async () => { },
 };
 
-const RerenderContext = React.createContext({ rerenderCounter: 0, setRerenderCounter: (value) => { } });
+const RerenderContext = React.createContext({ counter: 0 });
 /**
- * This provider is used to force re-renders in the test environment, since tanstack router does not support re-render.
+ * Provides a rerender signal via context to force re-renders in tests.
+ * TanStack Router wraps Match/MatchInner in React.memo, which blocks RTL's rerender() from
+ * propagating to the hook under test. React context changes bypass React.memo boundaries,
+ * so changing the context value triggers a re-render in any descendant consuming RerenderContext.
+ *
+ * The value is intentionally wrapped in a new object on every render. This ensures the context
+ * identity always changes -- even when the external counter prop hasn't changed (e.g. during
+ * HookRenderer's automatic rerender) -- so consumers are always notified.
  */
-const RerenderProvider = ({ children, counter }) => {
-    const [rerenderCounter, setRerenderCounter] = React.useState(0);
-    React.useEffect(() => {
-        if (counter && rerenderCounter !== counter && rerenderCounter !== 0) {
-            setRerenderCounter(counter);
-        }
-    }, [rerenderCounter, counter]);
-    return (jsxRuntime.jsx(RerenderContext.Provider, { value: { rerenderCounter, setRerenderCounter }, children: children }));
-};
+const RerenderProvider = ({ children, counter }) => (jsxRuntime.jsx(RerenderContext.Provider, { value: { counter }, children: children }));
 /**
- * This hook is used to get the rerender counter.
+ * Returns the current rerender counter from context.
  */
-const useRerenderCounter = () => {
-    return React.useContext(RerenderContext);
-};
+const useRerenderCounter = () => React.useContext(RerenderContext).counter;
 
 /**
- * This component is used to force re-renders in the test environment, since tanstack router does not support re-render.
+ * Subscribes to RerenderContext so this subtree re-renders when the counter changes,
+ * even when nested inside React.memo boundaries (like TanStack Router's Match/MatchInner).
+ *
+ * Consuming the context alone is not enough: React will bail out of re-rendering children
+ * if the element references haven't changed. createElement produces new element instances
+ * with a changed prop, which forces React to reconcile and re-render the test component.
  */
 const RerenderComponent = ({ children }) => {
-    const { rerenderCounter } = useRerenderCounter();
-    return (jsxRuntime.jsx("div", { "data-rerender-counter": `rerender-${rerenderCounter}`, children: React.Children.map(children, child => React.isValidElement(child)
+    const counter = useRerenderCounter();
+    return (jsxRuntime.jsx(jsxRuntime.Fragment, { children: React.Children.map(children, child => React.isValidElement(child)
             ? React.createElement(child.type, {
                 ...child.props,
                 key: child.key,
-                "data-rerender-counter": rerenderCounter,
+                "data-rerender-counter": counter,
             })
             : child) }));
 };

package/index.esm2.js

@@ -1,7 +1,7 @@
 import { SortOrder, AssetSortByProperty } from '@trackunit/iris-app-runtime-core-api';
-import { jsx, jsxs, Fragment } from 'react/jsx-runtime';
+import { jsx, Fragment, jsxs } from 'react/jsx-runtime';
 import * as React from 'react';
-import React__default, { createContext, useState, useEffect, useContext, Children, createElement, isValidElement, useRef, useCallback, useMemo } from 'react';
+import React__default, { createContext, useContext, Children, createElement, isValidElement, useRef, useEffect, useCallback, useMemo, useState } from 'react';
 import * as DeprecatedReactTestUtils from 'react-dom/test-utils';
 import ReactDOM from 'react-dom';
 import * as ReactDOMClient from 'react-dom/client';
@@ -13468,36 +13468,38 @@ const mockWidgetConfigContext = {
     closeEditMode: async () => { },
 };
 
-const RerenderContext = createContext({ rerenderCounter: 0, setRerenderCounter: (value) => { } });
+const RerenderContext = createContext({ counter: 0 });
 /**
- * This provider is used to force re-renders in the test environment, since tanstack router does not support re-render.
+ * Provides a rerender signal via context to force re-renders in tests.
+ * TanStack Router wraps Match/MatchInner in React.memo, which blocks RTL's rerender() from
+ * propagating to the hook under test. React context changes bypass React.memo boundaries,
+ * so changing the context value triggers a re-render in any descendant consuming RerenderContext.
+ *
+ * The value is intentionally wrapped in a new object on every render. This ensures the context
+ * identity always changes -- even when the external counter prop hasn't changed (e.g. during
+ * HookRenderer's automatic rerender) -- so consumers are always notified.
  */
-const RerenderProvider = ({ children, counter }) => {
-    const [rerenderCounter, setRerenderCounter] = useState(0);
-    useEffect(() => {
-        if (counter && rerenderCounter !== counter && rerenderCounter !== 0) {
-            setRerenderCounter(counter);
-        }
-    }, [rerenderCounter, counter]);
-    return (jsx(RerenderContext.Provider, { value: { rerenderCounter, setRerenderCounter }, children: children }));
-};
+const RerenderProvider = ({ children, counter }) => (jsx(RerenderContext.Provider, { value: { counter }, children: children }));
 /**
- * This hook is used to get the rerender counter.
+ * Returns the current rerender counter from context.
  */
-const useRerenderCounter = () => {
-    return useContext(RerenderContext);
-};
+const useRerenderCounter = () => useContext(RerenderContext).counter;
 
 /**
- * This component is used to force re-renders in the test environment, since tanstack router does not support re-render.
+ * Subscribes to RerenderContext so this subtree re-renders when the counter changes,
+ * even when nested inside React.memo boundaries (like TanStack Router's Match/MatchInner).
+ *
+ * Consuming the context alone is not enough: React will bail out of re-rendering children
+ * if the element references haven't changed. createElement produces new element instances
+ * with a changed prop, which forces React to reconcile and re-render the test component.
  */
 const RerenderComponent = ({ children }) => {
-    const { rerenderCounter } = useRerenderCounter();
-    return (jsx("div", { "data-rerender-counter": `rerender-${rerenderCounter}`, children: Children.map(children, child => isValidElement(child)
+    const counter = useRerenderCounter();
+    return (jsx(Fragment, { children: Children.map(children, child => isValidElement(child)
             ? createElement(child.type, {
                 ...child.props,
                 key: child.key,
-                "data-rerender-counter": rerenderCounter,
+                "data-rerender-counter": counter,
             })
             : child) }));
 };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@trackunit/react-core-contexts-test",
-  "version": "1.12.40",
+  "version": "1.12.42",
   "repository": "https://github.com/Trackunit/manager",
   "license": "SEE LICENSE IN LICENSE.txt",
   "engines": {
@@ -10,11 +10,11 @@
     "@apollo/client": "3.13.8",
     "react": "19.0.0",
     "@tanstack/react-router": "1.114.29",
-    "@trackunit/shared-utils": "1.13.56",
+    "@trackunit/shared-utils": "1.13.57",
     "graphql": "^16.10.0",
     "@tanstack/router-core": "1.114.29",
-    "@trackunit/iris-app-runtime-core-api": "1.12.38",
-    "@trackunit/react-core-contexts-api": "1.13.38",
+    "@trackunit/iris-app-runtime-core-api": "1.12.39",
+    "@trackunit/react-core-contexts-api": "1.13.39",
     "es-toolkit": "^1.39.10"
   },
   "module": "./index.esm.js",

package/src/rerenderProvider/RerenderComponent.d.ts

@@ -1,7 +1,12 @@
-import { ReactNode } from "react";
+import { type ReactNode } from "react";
 /**
- * This component is used to force re-renders in the test environment, since tanstack router does not support re-render.
+ * Subscribes to RerenderContext so this subtree re-renders when the counter changes,
+ * even when nested inside React.memo boundaries (like TanStack Router's Match/MatchInner).
+ *
+ * Consuming the context alone is not enough: React will bail out of re-rendering children
+ * if the element references haven't changed. createElement produces new element instances
+ * with a changed prop, which forces React to reconcile and re-render the test component.
  */
 export declare const RerenderComponent: ({ children }: {
     children: ReactNode;
-}) => import("react/jsx-runtime").JSX.Element;
+}) => ReactNode;

package/src/rerenderProvider/RerenderProvider.d.ts

@@ -1,15 +1,19 @@
 import { ReactNode } from "react";
 /**
- * This provider is used to force re-renders in the test environment, since tanstack router does not support re-render.
+ * Provides a rerender signal via context to force re-renders in tests.
+ * TanStack Router wraps Match/MatchInner in React.memo, which blocks RTL's rerender() from
+ * propagating to the hook under test. React context changes bypass React.memo boundaries,
+ * so changing the context value triggers a re-render in any descendant consuming RerenderContext.
+ *
+ * The value is intentionally wrapped in a new object on every render. This ensures the context
+ * identity always changes -- even when the external counter prop hasn't changed (e.g. during
+ * HookRenderer's automatic rerender) -- so consumers are always notified.
  */
 export declare const RerenderProvider: ({ children, counter }: {
     children: ReactNode;
     counter: number;
-}) => import("react/jsx-runtime").JSX.Element;
+}) => ReactNode;
 /**
- * This hook is used to get the rerender counter.
+ * Returns the current rerender counter from context.
  */
-export declare const useRerenderCounter: () => {
-    rerenderCounter: number;
-    setRerenderCounter: (value: number) => void;
-};
+export declare const useRerenderCounter: () => number;