[Snyk] Upgrade @reduxjs/toolkit from 1.9.5 to 1.9.7 #329
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 was automatically created by Snyk using the credentials of a real user.
![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to upgrade @reduxjs/toolkit from 1.9.5 to 1.9.7.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 2 versions ahead of your current version.
The recommended version was released on 9 months ago.
Issues fixed by the recommended upgrade:
SNYK-JS-SEMVER-3247795
SNYK-JS-WEBPACKDEVMIDDLEWARE-6476555
SNYK-JS-BRACES-6838727
SNYK-JS-FOLLOWREDIRECTS-6141137
SNYK-JS-FOLLOWREDIRECTS-6444610
SNYK-JS-FOLLOWREDIRECTS-6444610
SNYK-JS-SERIALIZEJAVASCRIPT-6147607
SNYK-JS-EXPRESS-6474509
Release notes
Package name: @reduxjs/toolkit
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: v1.9.6...v1.9.7
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: v1.9.5...v1.9.6
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: v1.9.4...v1.9.5
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: