Update dependency @reduxjs/toolkit to v2.5.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@reduxjs/toolkit (source)	2.2.7 -> 2.5.1

---

Release Notes

reduxjs/redux-toolkit (@​reduxjs/toolkit)

v2.5.1

Compare Source

This bugfix release fixes a logic issue with the new upsertQueryEntries util that sometimes kept entries in a pending state indefinitely.

Changelog

upsertQueryEntries fixes

Users reported that in some cases, use of upsertQueryEntries to insert RTKQ cache entries prevented any further refetches of that data from happening. After investigation, we found a logic mismatch for how we handle upserts vs the existing upsertQueryData util, which meant that sometimes the entry would be left in a pending state expecting a fulfilled action from a request ID that would never happen.

This release fixes that issue and ensures the updates and refetches happen correctly.

What's Changed

• Ensure upserted cache entries always get written by @​markerikson in https://github.com/reduxjs/redux-toolkit/pull/4768

Full Changelog: reduxjs/redux-toolkit@v2.5.0...v2.5.1

v2.5.0

Compare Source

This feature release updates the React peer dependency to work with React 19, and fixes an additional skip token issue.

Changelog

React 19 Compat

React 19 was just released! We've updated our peer dep to accept React 19, and updated our runtime and type tests to check against both React 18 and 19.

Also see React-Redux v9.2.0 for the same peer dep update.

Other Fixes

We previously fixed an issue with the RTKQ core where serializeQueryArgs callbacks could be called with skipToken, potentially leading to errors. We've fixed an additional location in the useQuery hooks where that could happen as well.

What's Changed

• Migrate to React 19 by @​aryaemami59 in https://github.com/reduxjs/redux-toolkit/pull/4409
• Handle additional serializeQueryArgs + skipToken case by @​markerikson in https://github.com/reduxjs/redux-toolkit/pull/4762

Full Changelog: reduxjs/redux-toolkit@v2.4.0...v2.5.0

v2.4.0

Compare Source

This feature release includes multiple tweaks and fixes to RTK Query functionality, additional exported TS types, and drops support for TS versions earlier than 5.0.

Changelog

RTK Query Improvements

Lazy query hooks can now be reset.

retry.fail now accepts meta as a second argument.

Tag invalidation arrays now ignore nullish values.

We did some small internal refactoring around Maps and default values that shrank bundle size slightly.

Bugfixes

Passing skipToken to a query hook now bails out before running any other logic, which fixes cases where serializeQueryArgs previously threw an error because there were no args to process.

The autoBatchEnhancer now reads window.requestAnimationFrame later, which it to work properly with Jest fake timers.

We fixed cases where the hook result isSuccess flag would briefly flicker to false when switched to a different cache entry that was uninitialized, and would briefly flicker to true when refetching a query that previously errored.

The listener middleware previously had inconsistent logic checks for comparing against existing listener entries (effect + type, vs effect only). It now always checks both effect + type.

Additional TS Types

We now export Typed[Query|Mutation]OnQueryStarted helpers to let you define onQueryStarted callbacks outside of createApi if desired.

We also now export a CreateAsyncThunkFunction type that can be used to type userland wrappers around createAsyncThunk.

TS Support Matrix Updates

We've historically tried to maintain TS backwards compatibility as long as possible, and made occasional updates to our TS support matrix in minor versions over time. As of RTK 2.3.0, we officially supported back through TS 4.7.

As of this release, we're tweaking that support policy to match the policy used by DefinitelyTyped:

Definitely Typed only tests packages on versions of TypeScript that are less than 2 years old

Given that, we've dropped official support for TS versions earlier than 5.0. (RTK may work with those versions, but we no longer test against them and won't try to fix issues with those versions.)

We'll continue to update our TS support matrix over time based on that 2-year rolling window.

What's Changed

• add example to reproduce defect of serializeQueryArgs with skipToken by @​Themezv in https://github.com/reduxjs/redux-toolkit/pull/4708
• Read window.rAF later to allow fake timers to work correctly by @​ensconced in https://github.com/reduxjs/redux-toolkit/pull/4701
• Add type helpers for OnQueryStarted callbacks by @​aryaemami59 in https://github.com/reduxjs/redux-toolkit/pull/4713
• Add a type for createAsyncThunk without the withTypes method by @​EskiMojo14 in https://github.com/reduxjs/redux-toolkit/pull/4667
• Add ability to reset lazy query hooks by @​alexmotoc in https://github.com/reduxjs/redux-toolkit/pull/4689
• Ignore nullish values in tag invalidations by @​pierroberto in https://github.com/reduxjs/redux-toolkit/pull/4671
• Allow passing meta to retry.fail, and passing baseQuery to ensure types match by @​EskiMojo14 in https://github.com/reduxjs/redux-toolkit/pull/4723
• Keep isSuccess: true when switching to an uninitialized cache entry by @​markerikson in https://github.com/reduxjs/redux-toolkit/pull/4731
• Keep isSuccess consistent when refetching after an error by @​markerikson in https://github.com/reduxjs/redux-toolkit/pull/4732
• Update to new version of upsert proposal, and fix listener equality checks by @​EskiMojo14 in https://github.com/reduxjs/redux-toolkit/pull/4735

Full Changelog: reduxjs/redux-toolkit@v2.3.0...v2.4.0

v2.3.0

Compare Source

This feature release adds a new RTK Query upsertQueryEntries util to batch-upsert cache entries more efficiently, passes through additional values for use in prepareHeaders, and exports additional TS types around query options and selectors.

Changelog

upsertQueryEntries

RTK Query already had an upsertQueryData thunk that would upsert a single cache entry. However, some users wanted to upsert many cache entries (potentially hundreds or thousands), and found that upsertQueryData had poor performance in those cases. This is because upsertQueryData runs the full async request handling sequence, including dispatching both pending and fulfilled actions, each of which run the main reducer and update store subscribers. That means there's 2N store / UI updates per item, so upserting hundreds of items becomes extremely perf-intensive.

RTK Query now includes an api.util.upsertQueryEntries action that is meant to handle the batched upsert use case more efficiently. It's a single synchronous action that accepts an array of many {endpointName, arg, value} entries to upsert. This results in a single store update, making this vastly better for performance vs many individual upsertQueryData calls.

We see this as having two main use cases. The first is prefilling the cache with data retrieved from storage on app startup (and it's worth noting that upsertQueryEntries can accept entries for many different endpoints as part of the same array).

The second is to act as a "pseudo-normalization" tool. RTK Query is not a "normalized" cache. However, there are times when you may want to prefill other cache entries with the contents of another endpoint, such as taking the results of a getPosts list endpoint response and prefilling the individual getPost(id) endpoint cache entries, so that components that reference an individual item endpoint already have that data available.

Currently, you can implement the "pseudo-normalization" approach by dispatching upsertQueryEntries in an endpoint lifecycle, like this:

const api = createApi({
  endpoints: (build) => ({
    getPosts: build.query<Post[], void>({
      query: () => '/posts',
      async onQueryStarted(_, { dispatch, queryFulfilled }) {
        const res = await queryFulfilled
        const posts = res.data

        // Pre-fill the individual post entries with the results
        // from the list endpoint query
        dispatch(
          api.util.upsertQueryEntries(
            posts.map((post) => ({
              endpointName: 'getPost',
              arg: { id: post.id },
              value: post,
            })),
          ),
        )
      },
    }),
    getPost: build.query<Post, Pick<Post, 'id'>>({
      query: (post) => `post/${post.id}`,
    }),
  }),
})

Down the road we may add a new option to query endpoints that would let you provide the mapping function and have it automatically update the corresponding entries.

For additional comparisons between upsertQueryData and upsertQueryEntries, see the upsertQueryEntries API reference.

prepareHeaders Options

The prepareHeaders callback for fetchBaseQuery now receives two additional values in the api argument:

• arg: the URL string or FetchArgs object that was passed in to fetchBaseQuery for this endpoint
• extraOptions: any extra options that were provided to the base query

Additional TS Types

We've added a TypedQueryStateSelector type that can be used to pre-type selectors for use with selectFromResult:

const typedSelectFromResult: TypedQueryStateSelector<
  PostsApiResponse,
  QueryArgument,
  BaseQueryFunction,
  SelectedResult
> = (state) => ({ posts: state.data?.posts ?? EMPTY_ARRAY })

function PostsList() {
  const { posts } = useGetPostsQuery(undefined, {
    selectFromResult: typedSelectFromResult,
  })
}

We've also exported several additional TS types around base queries and tag definitions.

What's Changed

• Fix serializeQueryArgs type by @​Reedgern in https://github.com/reduxjs/redux-toolkit/pull/4658
• Add the TypedQueryStateSelector helper type by @​aryaemami59 in https://github.com/reduxjs/redux-toolkit/pull/4656
• Pass query args to prepareHeaders function by @​kyletsang in https://github.com/reduxjs/redux-toolkit/pull/4638
• Implement a util function to batch-upsert cache entries by @​markerikson in https://github.com/reduxjs/redux-toolkit/pull/4561
• fetchBaseQuery: expose extraOptions to prepareHeaders by @​phryneas in https://github.com/reduxjs/redux-toolkit/pull/4291

Full Changelog: reduxjs/redux-toolkit@v2.2.8...v2.3.0

v2.2.8

Compare Source

This bugfix release fixes a long-standing issue with RTK Query lazy query triggers returning stale data in some cases, fixes an error handling issue in RTK Query, and exports additional TS types.

Changelog

Lazy Query Trigger Handling

We'd had a couple long-standing issues reporting that const result = await someLazyQueryTrigger() sometimes returned stale data, especially if a mutation had just invalidated that query's tag.

We finally got a good repro of this issue and identified it as a mis-written call inside of the middleware that skipped past the necessary handling to activate the correct query status tracking in that scenario. This should now be fixed.

Other Changes

Timeout handling in RTKQ endpoints should now correctly throw a timeout-related error instead of an AbortError.

Base queries now have access to the current queryCacheKey value so it can be used in deciding query logic.

We've exported several more TS types related to query options, as some users have been depending on those even though they previously weren't part of the public API.

What's Changed

• Export QueryExtraOptions and MutationExtraOptions by @​aryaemami59 in https://github.com/reduxjs/redux-toolkit/pull/4556
• Fix mangleErrors not preserving different error types by @​aryaemami59 in https://github.com/reduxjs/redux-toolkit/pull/4586
• Add the TypedUseQueryStateOptions helper type by @​aryaemami59 in https://github.com/reduxjs/redux-toolkit/pull/4604
• feat(baseQuery): expose queryCacheKey in baseQuery by @​HaakonSvane in https://github.com/reduxjs/redux-toolkit/pull/4636
• Fix AbortError being triggered incorrectly on createApi endpoint timeout by @​andrejpavlovic in https://github.com/reduxjs/redux-toolkit/pull/4628
• type: export QueryReturnValue by @​hornta in https://github.com/reduxjs/redux-toolkit/pull/4640
• call initiate to refetch queries from middleware by @​phryneas in https://github.com/reduxjs/redux-toolkit/pull/4651

Full Changelog: reduxjs/redux-toolkit@v2.2.7...v2.2.8

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.