spekni
spekni copied to clipboard
Update dependency react-redux to v8.1.0
This PR contains the following updates:
Package | Change | Age | Adoption | Passing | Confidence |
---|---|---|---|---|---|
react-redux | 8.0.2 -> 8.1.0 |
Release Notes
reduxjs/react-redux
v8.1.0
This feature release adds new development-mode safety checks for common errors (like poorly-written selectors), adds a workaround to fix crash errors when React-Redux hooks are imported into React Server Component files, and updates our hooks API docs page with improved explanations and updated links.
Changelog
Development Mode Checks for useSelector
We've had a number of users tell us over time that it's common to accidentally write selectors that have bad behavior and cause performance issues. The most common causes of this are either selectors that unconditionally return a new reference (such as state => state.todos.map()
without any memoization ), or selectors that actually return the entire root state ( state => state
).
We've updated useSelector
to add safety checks in development mode that warn if these incorrect behaviors are detected:
- Selectors will be called twice with the same inputs, and
useSelector
will warn if the results are different references -
useSelector
will warn if the selector result is actually the entire rootstate
By default, these checks only run once the first time useSelector
is called. This should provide a good balance between detecting possible issues, and keeping development mode execution performant without adding many unnecessary extra selector calls.
If you want, you can configure this behavior globally by passing the enum flags directly to <Provider>
, or on a per-useSelector
basis by passing an options object as the second argument:
// Example: globally configure the root state "noop" check to run every time
<Provider store={store} noopCheck="always">
{children}
</Provider>
// Example: configure `useSelector` to specifically run the reference checks differently:
function Component() {
// Disable check entirely for this selector
const count = useSelector(selectCount, { stabilityCheck: 'never' })
// run once (default)
const user = useSelector(selectUser, { stabilityCheck: 'once' })
// ...
}
This goes along with the similar safety checks we've added to Reselect v5 alpha as well.
Context Changes
We're still trying to work out how to properly use Redux and React Server Components together. One possibility is using RTK Query's createApi
to define data fetching endpoints, and using the generated thunks to fetch data in RSCs, but it's still an open question.
However, users have reported that merely importing any React-Redux API in an RSC file causes a crash, because React.createContext
is not defined in RSC files. RTKQ's React-specific createApi
entry point imports React-Redux, so it's been unusable in RSCs.
This release adds a workaround to fix that issue, by using a proxy wrapper around our singleton ReactReduxContext
instance and lazily creating that instance on demand. In testing, this appears to both continue to work in all unit tests, and fixes the import error in an RSC environment. We'd appreciate further feedback in case this change does cause any issues for anyone!
We've also tweaked the internals of the hooks to do checks for correct <Provider>
usage when using a custom context, same as the default context checks.
Docs Updates
We've cleaned up some of the Hooks API reference page, and updated links to the React docs.
What's Changed
- check for Provider even when using custom context by @​EskiMojo14 in https://github.com/reduxjs/react-redux/pull/1990
- Add a stability check, to see if selector returns stable result when called with same parameters. by @​EskiMojo14 in https://github.com/reduxjs/react-redux/pull/2000
- Add an E2E-ish test that verifies behavior when imported into RSCs by @​markerikson in https://github.com/reduxjs/react-redux/pull/2030
- lazily create Context for RSC compat by @​phryneas in https://github.com/reduxjs/react-redux/pull/2025
- Add warning for selectors that return the entire state by @​EskiMojo14 in https://github.com/reduxjs/react-redux/pull/2022
Full Changelog: https://github.com/reduxjs/react-redux/compare/v8.0.7...v8.1.0
v8.0.7
This release updates the peer dependencies to accept Redux Toolkit, and accept the ongoing RTK and Redux core betas as valid peer deps.
Note: These changes were initially in 8.0.6, but that had a typo in the peer deps that broke installation. Sorry!
What's Changed
- Bump Redux peer deps to accept 5.0 betas, and bump RTK dev dep by @​markerikson in https://github.com/reduxjs/react-redux/pull/2017
-
d45204f
: Fix broken RTK peer dep
Full Changelog: https://github.com/reduxjs/react-redux/compare/v8.0.5...v8.0.7
v8.0.6
~~This release updates the peer dependencies to accept Redux Toolkit, and accept the ongoing RTK and Redux core betas as valid peer deps.~~
This release has a peer deps typo that breaks installation - please use 8.0.7 instead !
What's Changed
- Bump Redux peer deps to accept 5.0 betas, and bump RTK dev dep by @​markerikson in https://github.com/reduxjs/react-redux/pull/2017
Full Changelog: https://github.com/reduxjs/react-redux/compare/v8.0.5...v8.0.6
v8.0.5
This release fixes a few minor TS issues.
What's Changed
-
Provider
: pass state (S
) generic through toProviderProps
by @​OliverJAsh in https://github.com/reduxjs/react-redux/pull/1960 - wrap
equalityFn
type inNoInfer
by @​phryneas in https://github.com/reduxjs/react-redux/pull/1965 - Fix wrapped component prop types when passing nullish mapDispatchToProps by @​marconi1992 in https://github.com/reduxjs/react-redux/pull/1928
Full Changelog: https://github.com/reduxjs/react-redux/compare/v8.0.4...v8.0.5
v8.0.4
This patch release fixes some minor TS types issues, and updates the rarely-used areStatesEqual
option for connect
to now pass through ownProps
for additional use in determining which pieces of state to compare if desired.
Note: 8.0.3 was accidentally published without one of these fixes. Use 8.0.4 instead.
Changelog
TS Fixes
We've fixed an import of React
that caused issues with the allowSyntheticDefaultImports
TS compiler flag in user projects.
connect
already accepted a custom context instance as props.context
, and had runtime checks in case users were passing through a real value with app data as props.context
instead. However, the TS types did not handle that case, and this would fail to compile. If your own component expects props.context
with actual data, connect
's types now use that type instead.
The ConnectedProps<T>
type had a mismatch with React's built-in React.ComponentProps<Component>
type, and that should now work correctly.
Other Changes
The areStatesEqual
option to connect
now receives ownProps
as well, in case you need to make a more specific comparison with certain sections of state.
The new signature is:
{
areStatesEqual?: (
nextState: State,
prevState: State,
nextOwnProps: TOwnProps,
prevOwnProps: TOwnProps
) => boolean
}
What's Changed
- Don't require allowSyntheticDefaultImports: true by @​apepper in https://github.com/reduxjs/react-redux/pull/1924
- Fixed type issue with
ComponentProps
from older@types/react
by @​Andarist in https://github.com/reduxjs/react-redux/pull/1956 - connect: pass ownProps to areStatesEqual by @​jspurlin in https://github.com/reduxjs/react-redux/pull/1951
- Omit built-in context prop if user component props include context by @​markerikson in https://github.com/reduxjs/react-redux/pull/1958
Full Changelog: https://github.com/reduxjs/react-redux/compare/v8.0.2...v8.0.4
v8.0.3
This release was accidentally published without an intended fix - please use v8.0.4 instead
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 has been generated by Mend Renovate. View repository job log here.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
spekni | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Jun 13, 2023 5:19am |