Update dependency @reduxjs/toolkit to v1.9.7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@reduxjs/toolkit (source)	1.9.0 → 1.9.7

---

Release Notes

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

v1.9.7

Compare Source

This bugfix release rewrites the RTKQ hook TS types to significantly improve TS perf.

Changelog

RTKQ TS Perf

A number of users had reported that Intellisense for RTKQ API objects was extremely slow (multiple seconds) - see discussion in #​3214 . We did some perf investigation on user-provided examples, and concluded that the biggest factor to slow RTKQ TS perf was the calculation of hook names like useGetPokemonQuery, which was generating a large TS union of types.

We've rewritten that hook names type calculation to use mapped types and a couple of intersections. In a specific user-provided stress test repo, it dropped TS calculation time by 60% (2600ms to 1000ms).

There's more potential work we can do to improve things, but this seems like a major perf improvement worth shipping now.

What's Changed

• chore: Switch 4.9.2-rc to 4.9.5 since 4.9.5 has been released in TypeScript by @​kahirokunn in #​3772
• Copy of "Work around known TS bug with type inference #​3761" by @​julian-ford in #​3777
• Rework named hooks type (v1.9) by @​EskiMojo14 in #​3769

Full Changelog: reduxjs/redux-toolkit@v1.9.6...v1.9.7

v1.9.6

Compare Source

This bugfix release adds a new dev-mode middleware to catch accidentally dispatching an action creator, adds a new listener middleware option around waiting for forks, adds a new option to update provided tags when updateQueryData is used, reworks internal types to better handle uses with TS declaration output, and fixes a variety of small issues.

Changelog

Action Creator Dev Check Middleware

RTK already includes dev-mode middleware that check for the common mistakes of accidentally mutating state and putting non-serializable values into state or actions.

Over the years we've also seen a semi-frequent error where users accidentally pass an action creator reference to dispatch, instead of calling it and dispatching the action it returns.

We've added another dev-mode middleware that specifically catches this error and warns about it.

Additional Options

The listener middleware's listenerApi.fork() method now has an optional autoJoin flag that can be used to keep the effect from finishing until all active forked tasks have completed.

updateQueryData now has an updateProvidedTags option that will force a recalculation of that endpoint's provided tags. It currently defaults to false, and we'll likely turn that to true in the next major.

Other Fixes

The builder.addCase method now throws an error if a type string is empty.

fetchBaseQuery now uses an alternate method to clone the original Request in order to work around an obscure Chrome bug.

The immutability middleware logic was tweaked to avoid a potential stack overflow.

Types Changes

The internal type imports have been reworked to try to fix "type portability" issues when used in combination with TS declaration outputs.

A couple additional types were exported to help with wrapping createAsyncThunk.

What's Changed

• create action creator middleware by @​EskiMojo14 in #​3414
• Implement auto fork joining by @​ericanderson in #​3407
• types: make it easier to wrap createAsyncThunk by @​shrouxm in #​3393
• Fixed Stackoverflow bug if children prop is a ref to root/parent object by @​cheprasov in #​3428
• Fix TransformedResponse type to unwrap promise by @​EskiMojo14 in #​3500
• Throw error when type is empty in builder.addCase by @​chawes13 in #​3572
• [RED-23] fix: Updated type references to resolve portable types issue by @​tdurnford in #​3728
• add option to update provided tags by @​dutzi in #​3255
• [RED-26] Remove Request.clone() usage in fetchBaseQuery by @​alex-vukov in #​3720
• Try working around TS 4.1 mismatch by @​markerikson in #​3739

Full Changelog: reduxjs/redux-toolkit@v1.9.5...v1.9.6

v1.9.5

Compare Source

This bugfix release includes notable improvements to TS type inference when using the enhancers option in configureStore, and updates the listener middleware to only check predicates if the dispatched value is truly an action object.

What's Changed

• update to latest remark-typescript-tools by @​EskiMojo14 in #​3311
• add isAction helper function, and ensure listener middleware only runs for actions by @​EskiMojo14 in #​3372
• Allow inference of enhancer state extensions, and fix inference when using callback form by @​EskiMojo14 in #​3207

Full Changelog: reduxjs/redux-toolkit@v1.9.4...v1.9.5

v1.9.4

Compare Source

This bugfix release includes tweaks to RTKQ options handling, tweaks for perf updates, dependency updates, and updates to our CI tooling.

Also, please check out our ongoing RTK 2.0 alpha releases! They have significant improvements to bundle size, ESM/CJS compatibility, TS typings, and reducer update performance. We're looking for real-world feedback on behavior, performance, and any issues you might run into.

Changelog

RTK Query Options Updates

Passing transformResponse as part of enhanceEndpoints can now override the TS type of the original data.

fetchBaseQuery now properly checks for a global responseHandler option.

Performance and Internals

RTK Query now uses Immer's original() to do comparisons inside of copyWithStructuralSharing, which should significantly speed up performance when applying changes from re-fetched data.

RTKQ's internal subscriptionUpdated action is now marked as batchable.

We've updated dependencies to Immer 9.0.21, Reselect 4.1.8, and Redux 4.2.1.

CI Updates

We've added a suite of example apps built with different frameworks such as CRA 4, CRA 5, Next, and Vite, as well as examples that check for compatibility in Node with CJS and ESM modes and with various TS module resolution modes.

What's Changed

• Test published artifacts in CI by @​markerikson in #​3213
• Use Git revision in version and add Node CI examples by @​markerikson in #​3258
• Add arethetypeswrong automated CLI check by @​markerikson in #​3294
• Add attw CLI option to treat problems as non-errors by @​markerikson in #​3316
• Use original instead of immer draft for perf by @​GeorchW in #​3270
• enable enhanceEndpoints.transformResponse to override ResultType by @​dmitrigrabov in #​2953
• Fix global responseHandler being used in fetchBaseQuery by @​praxxis in #​3137
• reset internalState.currentSubscriptions on resetApiState by @​phryneas in #​3333
• Bump deps and mark subscriptionUpdated as autobatched by @​markerikson in #​3364

Full Changelog: reduxjs/redux-toolkit@v1.9.3...v1.9.4

v1.9.3

Compare Source

This release fixes a couple issues with the skip/skipToken options for query hooks, and makes a small perf tweak to serializing query args.

Changelog

Skip Behavior

We made a change in v1.9.0 that tried to make some skip behavior more consistent, including clearing out the cached data. However, we had overlooked that our own docs actually said "skipping a query will keep the cached data", and several users pointed this out as they'd been relying on that behavior.

We've reverted that change. Now, setting {skip: true} or skipToken for a query with existing results will keep the data value (reflecting the last successful query), but currentData will be undefined (reflecting the current settings).

We also identified and fixed an issue that could cause subscription entries to leak under a specific combination of timing and settings changes.

Query Arg Serialization Perf

RTKQ relies on serializing query arguments to serve as the cache keys, with the default using JSON.stringify() + some logic for sorting keys. There was a report that in some apps, large query arg objects could take a while to stringify and this was being done repeatedly. We've added a WeakMap-based cache for query args to avoid re-serializing existing arg values.

What's Changed

• Revert "clear data on skip" back to its original behavior by @​markerikson in #​3188
• Use a WeakMap cache for query arg serialization for perf by @​markerikson in #​3193

Full Changelog: reduxjs/redux-toolkit@v1.9.2...v1.9.3

v1.9.2

Compare Source

This bugfix release fixes a memory leak in createListenerMiddleware, optimizes performance inside serializableMiddleware, adds new options for fetchBaseQuery, adds support for path RegExp exclusions in serializableMiddleware and immutabilityMiddleware, and improves some TS types.

Changelog

Bug Fixes

createListenerMiddleware had a memory leak that turned out to be due to use of Promise.race(). We've restructured the logic to fix that.

fetchBaseQuery now correctly combines global options with endpoint / default options in all cases.

New Options

fetchBaseQuery now supports a jsonReplacer option that will be used when processing JSON.

Both dev check middleware now support regular expressions in the ignoredPaths array in addition to strings. This adds extra flexibility in skipping certain fields.

TS Changes

The CaseReducer type was sometimes incorrectly inferring its return type in rare cases. That's been fixed.

The isAnyOf/isAllOf matcher function TS types have been tweaked to not require an individual first parameter. This allows spreading arrays of matchers as arguments, like const isLoading = isAnyOf(...interestingPendingThunksArray).

Other Changes

The serializableMiddleware now uses a WeakSet if available to cache values it's seen. This should significantly speed up checks against large state values in development builds.

What's Changed

• fix CaseReducer to infer from argument, not return value by @​phryneas in #​3054
• fetchBaseQuery | Add jsonReplacer param by @​tophep in #​2904
• Support RegExp in ignoredPaths/ignoredActionPaths by @​markerikson in #​3129
• fix(types): export ThunkWithReturnValue interface by @​giomogna in #​3108
• remove unnecessary fetchBaseQuery defaults by @​phryneas in #​3062
• make isAnyOf friendly for mapped matchers, but making argument optional by @​megagon in #​3123
• raceWithSignal method instead of Promise.race by @​phryneas in #​3021
• Fix lint problems and enable linting on CI by @​thorn0 in #​2992
• Add caching to serializableStateInvariantMiddleware by @​GeorchW in #​3115
• Allow TS isolatedModules flag to be set for safer transpilation by @​matmannion in #​2911

Full Changelog: reduxjs/redux-toolkit@v1.9.1...v1.9.2

v1.9.1

Compare Source

This bugfix release fixes assorted issues that were reported with RTK 1.9.0, and adds a few additional requested tweaks and improvements.

Changelog

Fixes

The createAsyncThunk.withTypes function was fully broken (it type-checked correctly, but pointed to the wrong function due to a name shadowing issue). That now works correctly.

The maxRetries option for RTKQ was inadvertently filtering out 0 values, and those are now accepted.

fulfillWithValue had incorrect types that made it appear as if the data was nested an additional level deeper. The types are now correct.

The ActionCreatorWithoutPayload type was tweaked to force an error when an action creator is accidentally called with an argument, which happens in cases like onClick={todoAdded}. This avoids accidentally passing values like React event objects as the payload.

Timer handling for batchActions and autoBatchEnhancer now works in more JS runtime environments.

Other Changes

The TagDescription type is now exported from RTKQ.

API endpoints now have a .name field containing the endpoint name, such as "getPokemon".

Calling promise.abort() on a createAsyncThunk promise before an async condition resolves will now be treated as if the condition itself returned false, bailing out and not dispatching anything.

The merge option now receives a third argument containing {arg, baseQueryMeta, fulfilledTimeStamp, requestId}, in case that info is useful in deciding how to merge.

The @reduxjs/rtk-codemods package has been updated to fix cases where the createSliceBuilder codemod didn't preserve fields with function variable arguments, like [todoAdded]: adapter.addOne. That package has been updated to v0.0.3.

What's Changed

• fix createAsyncThunk.withTypes by @​phryneas in #​2885
• Update timer polyfills to work in more environments by @​markerikson in #​2887
• Retry now checks whether potential retry counts are undefined, rather than boolean, in order to avoid filtering out 0's by @​OliverRadini in #​2958
• Fix multiple small issues with 1.9 by @​markerikson in #​2964
• fulfillWithValue should infer return value by @​phryneas in #​2888
• Fix Identifier/MemberExpression values in createSliceBuilder codemod by @​kyletsang in #​2881
• Additional 1.9.1 fixes by @​markerikson in #​2965

Full Changelog: reduxjs/redux-toolkit@v1.9.0...v1.9.1

---

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.