swr

Summary In #4208, \immutable\ middleware was updated to set \config.refreshInterval = 0\ to prevent inheriting global \SWRConfig\ \ efreshInterval\. However, because this was unconditionally executed inside the middleware, it ignored explicit hook-level \ efreshInterval\ options passed directly to \useSWRImmutable\ (e.g. \useSWRImmutable(key, fetcher, { refreshInterval: 100 })\). Changes Removed unconditional \config.refreshInterval = 0\ from the \immutable\ middleware in \src/immutable/index.ts\. Defined \useSWRImmutable\ with default \ efreshInterval: 0\ in \hookConfig\ (\{ refreshInterval: 0, ...config, use: (config.use []).concat(immutable) }\) so that global config polling is ignored while explicit hook options are preserved. Added a unit test in \ est/use-swr-immutable.test.tsx\ verifying hook-level \ efreshInterval\ revalidations. Closes #4322

Problem: When using \mutate\ with both \optimisticData\ and an async data function that return structurally identical data (but different array references), SWR populates the cache with the new reference. Even though \useSWR\ evaluates that the snapshots are deeply equal and initially returns the old \memorizedSnapshot\ object, it updates the snapshot's \data\ field to the new cache reference via \memorizedSnapshot.data = newSnapshot.data\. This breaks referential equality of the returned \data\, causing React child components (like \React.memo\ lists) to unnecessarily re-render the whole array, despite the content remaining exactly the same. Solution: In \src/index/use-swr.ts\, when \compareResult\ is evaluated as true (indicating structural equality), we conditionally preserve \memorizedSnapshot.data\ if it wasn't a tracked field that we should ignore. If they are structurally identical, we skip assigning the new data reference to \memorizedSnapshot.data\, thereby preserving referential equality. This ensures that mutations won't inadvertently break object references in the active hook instances. Changes Made: \src/index/use-swr.ts\: Updated the snapshot assignment inside \if (compareResult)\ to only update \memorizedSnapshot.data\ if \stateDependencies.data\ is false. \ est/test-issue-4180.test.tsx\: Added a test specifically reproducing the \mutate\ sequence on \useSWRInfinite\ to assert that the \data\ array reference does not change when the asynchronously fetched payload is structurally identical to the optimistic payload. Testing: Checked out the issue #4180 reproduction using \useSWRInfinite\ with an array payload in the new Jest test (\ est-issue-4180.test.tsx\). Verified that without the fix, the \data\ reference changed when the mutate promise resolved. Verified that with the fix, the \data\ array reference remains stable and the component only re-renders twice instead of three times for identical data. Ran all tests with \pnpm test\ to ensure no side effects on existing revalidation or subscription logic. Fixes #4180

Summary currently points at , but the published package contains instead. This updates the export target to match the emitted file name used in the package tarball. Reproduction Before this change, the react-server condition resolves to the missing file: The tarball contains: Validation Locally patched and verified the same resolution now points at the existing file: No package scripts were run for this check.