Update dependency @reduxjs/toolkit to v1.9.7 #9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.9.2
->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
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 optionalautoJoin
flag that can be used to keep the effect from finishing until all active forked tasks have completed.updateQueryData
now has anupdateProvidedTags
option that will force a recalculation of that endpoint's provided tags. It currently defaults tofalse
, and we'll likely turn that totrue
in the next major.Other Fixes
The
builder.addCase
method now throws an error if atype
string is empty.fetchBaseQuery
now uses an alternate method to clone the originalRequest
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
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 inconfigureStore
, and updates the listener middleware to only check predicates if the dispatched value is truly an action object.What's Changed
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 ofenhanceEndpoints
can now override the TS type of the original data.fetchBaseQuery
now properly checks for a globalresponseHandler
option.Performance and Internals
RTK Query now uses Immer's
original()
to do comparisons inside ofcopyWithStructuralSharing
, 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
arethetypeswrong
automated CLI check by @markerikson in https://github.com/reduxjs/redux-toolkit/pull/3294attw
CLI option to treat problems as non-errors by @markerikson in https://github.com/reduxjs/redux-toolkit/pull/3316responseHandler
being used infetchBaseQuery
by @praxxis in https://github.com/reduxjs/redux-toolkit/pull/3137resetApiState
by @phryneas in https://github.com/reduxjs/redux-toolkit/pull/3333subscriptionUpdated
as autobatched by @markerikson in https://github.com/reduxjs/redux-toolkit/pull/3364Full 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}
orskipToken
for a query with existing results will keep thedata
value (reflecting the last successful query), butcurrentData
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 aWeakMap
-based cache for query args to avoid re-serializing existing arg values.What's Changed
Full Changelog: reduxjs/redux-toolkit@v1.9.2...v1.9.3
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.
This PR has been generated by Mend Renovate. View repository job log here.