Update all dependencies #11
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/all"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
12.1.5
->13.4.0
13.5.0
->14.4.3
16.11.68
->18.11.6
18.0.21
->18.0.23
18.0.6
->18.0.7
4.0.17
->4.0.18
7.2.9
->8.0.4
Release Notes
testing-library/react-testing-library
v13.4.0
Compare Source
Features
v13.3.0
Compare Source
Features
globalThis
if available (#1070) (c80809a)v13.2.0
Compare Source
Features
v13.1.1
Compare Source
Bug Fixes
v13.1.0
Compare Source
Features
renderHook
(#991) (9535eff)v13.0.1
Compare Source
Bug Fixes
v13.0.0
Compare Source
Features
BREAKING CHANGES
createRoot
API by default which comes with a set of changes while also enabling support for concurrent features.To opt-out of this change you can use
render(ui, { legacyRoot: true } )
. But be aware that the legacy root API is deprecated in React 18 and its usage will trigger console warnings.testing-library/user-event
v14.4.3
Compare Source
Bug Fixes
types
field inexports
(#1029) (5bed8c6)v14.4.2
Compare Source
Bug Fixes
exports
field (#1022) (7839e29)v14.4.1
Compare Source
Bug Fixes
v14.4.0
Compare Source
Features
auxclick
events (#1003) (2852509)Bug Fixes
Control
onAltGraph
(#1003) (2852509)contextmenu
events withdetail: 0
(#1003) (2852509)PointerEvent.isPrimary
(#1003) (2852509)button
property on pointer events separately from legacy mouse events (#1003) (2852509)mousedown
andmouseup
happen on different elements (#1003) (2852509)mouseover
,mouseenter
andmousemove
on disabled elements (#1003) (2852509)mouse*
events perpointerdown
event handler (#1003) (2852509)*out
and*over
events when moving into / out of nested elements (#1003) (2852509)*enter
and*leave
events on ancestors (#1003) (2852509)v14.3.0
Compare Source
Features
v14.2.6
Compare Source
Bug Fixes
pointer-events: none
on previous target (#991) (6e4058b)v14.2.5
Compare Source
Bug Fixes
value
onHTMLSelectElement
(#989) (77a7fa8)v14.2.4
Compare Source
Bug Fixes
window.FileList
instead of implicit global (c88865d)v14.2.3
Compare Source
Bug Fixes
v14.2.2
Compare Source
Bug Fixes
HTMLInputElement.setRangeText()
(#984) (73443ec)v14.2.1
Compare Source
Performance Improvements
v14.2.0
Compare Source
Features
pointerEventsCheck
(#950) (31b7091)Bug Fixes
asyncWrapper
(#952) (6f55fee)v14.1.1
Compare Source
14.1.1 (2022-04-17)
Bug Fixes
globalThis
instead ofglobal
(#928) (497c14d)v14.1.0
Compare Source
Features
advanceTimers
option (#907) (627a5cf)Bug Fixes
maxlength
(#909) (f5049c4)v14.0.4
Compare Source
14.0.4 (2022-04-01)
Bug Fixes
HTMLInputElement.select()
(#898) (6d36828)v14.0.3
Compare Source
14.0.3 (2022-03-31)
Bug Fixes
focus
(#895) (06f12a6)v14.0.2
Compare Source
14.0.2 (2022-03-31)
Bug Fixes
v14.0.1
Compare Source
14.0.1 (2022-03-31)
Bug Fixes
v14.0.0
Compare Source
⚠ BREAKING CHANGES
skipPointerEvents
has been removed.Use
pointerEventsCheck: PointerEventsCheckLevel.Never
instead.init
parameter has been removed fromuserEvent.upload
.applyAccept
defaults totrue
.userEvent.paste
API has new parameters.{ctrl}
,{del}
,{esc}
no longer describe a key. Use{Control}
,{Delete}
,{Escape}
instead.{alt}
,{ctrl}
,{meta}
,{shift}
no longer imply not releasing the key. Use{Alt>}
,{Control>}
,{Meta>}
,{Shift>}
instead.init
parameter has been removed from these APIs:userEvent.click
userEvent.dblClick
userEvent.tripleClick
userEvent.hover
userEvent.unhover
userEvent.selectOptions
userEvent.deselectOptions
userEvent.upload
no longer supportsclickInit
as part of its
init
parameter.{selectall}
has been removed.keyCode
property on keyboard events has been removed.userEvent.clear
on an element which is not editable.userEvent.clear
from focussing/selecting content.focusTrap
option has been removed fromuserEvent.tab()
.userEvent.type
does no longer move the cursorif used with
skipClick=false
and withoutinitialSelectionStart
.This might break tests relying on unintended side-effects of the previous implementation.
Features
beforeinput
(#851) (8890bd6)pointer
API (#750) (c12ee44)setup
API (#746) (719ba03)userEvent.copy
anduserEvent.cut
(#787) (8727a2d)userEvent.tripleClick
API (#773) (0badabd)[Tab]
support (#767) (87470ff){Control}+[KeyA]
(#774) (ea9b18a)pointerEventsCheck
option (#823) (e2a5f43)MouseEventInit
(#784) (56ebf7d)userEvent.paste
(#785) (f8fe217)userEvent.clear
API (#779) (1cda1b1)Bug Fixes
:disabled
(#872) (1a00fdf)copy
/cut
(#866) (5423094)paste
(#862) (d3d71ac)createEvent
(#781) (da5b5b7)KeyboardEvent.charCode
onkeypress
(#771) (55e194a)<button/>
on[Enter]
(#808) (eca157a)activeElement
on click outside of focusable (#834) (d64167c)<label/>
(#810) (2c5d9f1)contextmenu
onmousedown
(#811) (e1c4cad)tabIndex>0
beforetabIndex=0
(#809) (1bc5945)focusTrap
option (#772) (a0412c0)visibility:hidden
(#799) (a747b0a)Miscellaneous Chores
clap-rs/clap
v4.0.18
Compare Source
Fixes
#[command(skip)]
to also work with enum variants with a valuereduxjs/react-redux
v8.0.4
Compare Source
This patch release fixes some minor TS types issues, and updates the rarely-used
areStatesEqual
option forconnect
to now pass throughownProps
for additional use in determining which pieces of state to compare if desired.Changelog
TS Fixes
We've fixed an import of
React
that caused issues with theallowSyntheticDefaultImports
TS compiler flag in user projects.connect
already accepted a custom context instance asprops.context
, and had runtime checks in case users were passing through a real value with app data asprops.context
instead. However, the TS types did not handle that case, and this would fail to compile. If your own component expectsprops.context
with actual data,connect
's types now use that type instead.The
ConnectedProps<T>
type had a mismatch with React's built-inReact.ComponentProps<Component>
type, and that should now work correctly.Other Changes
The
areStatesEqual
option toconnect
now receivesownProps
as well, in case you need to make a more specific comparison with certain sections of state.The new signature is:
What's Changed
ComponentProps
from older@types/react
by @Andarist in https://github.com/reduxjs/react-redux/pull/1956Full Changelog: https://github.com/reduxjs/react-redux/compare/v8.0.2...v8.0.4
v8.0.3
Compare Source
This release was accidentally published without an intended fix - please use v8.0.4 instead
v8.0.2
Compare Source
This patch release tweaks the behavior of
connect
to print a one-time warning when the obsoletepure
option is passed in, rather than throwing an error. This fixes crashes caused by libraries such asreact-beautiful-dnd
continuing to pass in that option (unnecessarily) to React-Redux v8.What's Changed
Full Changelog: https://github.com/reduxjs/react-redux/compare/v8.0.1...v8.0.2
v8.0.1
Compare Source
This release fixes an incorrect internal import of our
Subscription
type, which was causing TS compilation errors in some user projects. We've also listed@types/react-dom
as an optional peerDep. There are no runtime changes in this release.What's Changed
Subscription
causesnoImplicitAny
error by @vicrep in https://github.com/reduxjs/react-redux/pull/1910Full Changelog: https://github.com/reduxjs/react-redux/compare/v8.0.0...v8.0.1
v8.0.0
Compare Source
This major version release updates
useSelector
,connect
, and<Provider>
for compatibility with React 18, rewrites the React-Redux codebase to TypeScript (obsoleting use of@types/react-redux
), modernizes build output, and removes the deprecatedconnectAdvanced
API and thepure
option forconnect
.Overview, Compatibility, and Migration
Our public API is still the same (
<Provider>
,connect
anduseSelector/useDispatch
), but we've updated the internals to use the newuseSyncExternalStore
hook from React. React-Redux v8 is still compatible with all versions of React that have hooks (16.8+, 17.x, and 18.x; React Native 0.59+), and should just work out of the box.In most cases, it's very likely that the only change you will need to make is bumping the package version to
"react-redux": "^8.0"
.If you are using the rarely-used
connectAdvanced
API, you will need to rewrite your code to avoid that, likely by using the hooks API instead. Similarly, thepure
option forconnect
has been removed.If you are using Typescript, React-Redux is now written in TS and includes its own types. You should remove any dependencies on
@types/react-redux
.While not directly tied to React-Redux, note that the recently updated
@types/react@18
major version has changed component definitions to remove havingchildren
as a prop by default. This causes errors if you have multiple copies of@types/react
in your project. To fix this, tell your package manager to resolve@types/react
to a single version. Details:React issue #24304: React 18 types broken since release
Additionally, please see the React post on How to Ugprade to React 18 for details on how to migrate existing apps to correctly use React 18 and take advantage of its new features.
Changelog
React 18 Compatibility
React-Redux now requires the new
useSyncExternalStore
API in React 18. By default, it uses the "shim" package which backfills that API in earlier React versions, so React-Redux v8 is compatible with all React versions that have hooks (16.8+, and React Native 0.59+) as its acceptable peer dependencies.We'd especially like to thank the React team for their extensive support and cooperation during the
useSyncExternalStore
development effort. They specifically designeduseSyncExternalStore
to support the needs and use cases of React-Redux, and we used React-Redux v8 as a testbed for howuseSyncExternalStore
would behave and what it needed to cover. This in turn helped ensure thatuseSyncExternalStore
would be useful and work correctly for other libraries in the ecosystem as well.Our performance benchmarks show parity with React-Redux v7.2.5 for both
connect
anduseSelector
, so we do not anticipate any meaningful performance regressions.useSyncExternalStore
and BundlingThe
useSyncExternalStore
shim is imported directly in the main entry point, so it's always included in bundles even if you're using React 18. This adds roughly 600 bytes minified to your bundle size.If you are using React 18 and would like to avoid that extra bundle cost, React-Redux now has a new
/next
entry point. This exports the exact same APIs, but directly importsuseSyncExternalStore
from React itself, and thus avoids including the shim. You can alias"react-redux": "react-redux/next"
in your bundler to use that instead.SSR and Hydration
React 18 introduces a new
hydrateRoot
method for hydrating the UI on the client in Server-Side Rendering usage. As part of that, theuseSyncExternalStore
API requires that we pass in an alternate state value other than what's in the actual Redux store, and that alternate value will be used for the entire initial hydration render to ensure the initial rehydrated UI is an exact match for what was rendered on the server. After the hydration render is complete, React will then apply any additional changes from the store state in a follow-up render.React-Redux v8 supports this by adding a new
serverState
prop for<Provider>
. If you're using SSR, you should pass your serialized state to<Provider>
to ensure there are no hydration mismatch errors:TypeScript Migration and Support
The React-Redux library source has always been written in plain JS, and the community maintained the TS typings separately as
@types/react-redux
.We've (finally!) migrated the React-Redux codebase to TypeScript, using the existing typings as a starting point. This means that the
@types/react-redux
package is no longer needed, and you should remove that as a dependency.We've tried to maintain the same external type signatures as much as possible. If you do see any compile problems, please file issues with any apparent TS-related problems so we can review them.
The TS migration was a great collaborative effort, with many community members contributing migrated files. Thank you to everyone who helped out!
In addition to the "pre-typed"
TypedUseSelectorHook
, there's now also aConnect<State = unknown>
type that can be used as a "pre-typed" version ofconnect
as well.As part of the process, we also updated the repo to use Yarn 3, copied the typetests files from DefinitelyTyped and expanded them, and improved our CI setup to test against multiple TS versions.
Removal of the
DefaultRootState
typeThe
@types/react-redux
package, which has always been maintained by the community, included aDefaultRootState
interface that was intended for use with TS's "module augmentation" capability. Bothconnect
anduseSelector
used this as a fallback if no state generic was provided. When we migrated React-Redux to TS, we copied over all of the types from that package as a starting point.However, the Redux team specifically considers use of a globally augmented state type to be an anti-pattern. Instead, we direct users to extract the
RootState
andAppDispatch
types from the store setup, and create pre-typed versions of the React-Redux hooks for use in the app.Now that React-Redux itself is written in TS, we've opted to remove the
DefaultRootState
type entirely. State generics now default tounknown
instead.Technically the module augmentation approach can still be done in userland, but we discourage this practice.
Modernized Build Output
We've always targeted ES5 syntax in our published build artifacts as the lowest common denominator. Even the "ES module" artifacts with
import/export
keywords still were compiled to ES5 syntax otherwise.With IE11 now effectively dead and many sites no longer supporting it, we've updated our build tooling to target a more modern syntax equivalent to ES2017, which shrinks the bundle size slightly.
If you still need to support ES5-only environments, please compile your own dependencies as needed for your target environment.
Removal of Legacy APIs
We announced in 2019 that the legacy
connectAdvanced
API would be removed in the next major version, as it was rarely used, added internal complexity, and was also basically irrelevant with the introduction of hooks. As promised, we've removed that API.We've also removed the
pure
option forconnect
, which forced components to re-render regardless of whether props/state had actually changed if it was set tofalse
. This option was needed in some cases in the early days of the React ecosystem, when components sometimes relied on external mutable data sources that could change outside of rendering. Today, no one writes components that way, the option was barely used, and React 18'suseSyncExternalStore
strictly requires immutable updates. So, we've removed thepure
flag.Given that both of these options were almost never used, this shouldn't meaningfully affect anyone.
Changes
Due to the TS migration effort and number of contributors, this list covers just the major changes:
pure
removal by @Andarist in https://github.com/reduxjs/react-redux/pull/1859useSyncExternalStore
shim behavior and update React deps by @markerikson in https://github.com/reduxjs/react-redux/pull/1884DefaultRootState
type by @markerikson in https://github.com/reduxjs/react-redux/pull/1887serverState
behavior by @markerikson in https://github.com/reduxjs/react-redux/pull/1888peerDependencies
by @kyletsang in https://github.com/reduxjs/react-redux/pull/1893dispatchProp
arg inmergeProps
by @markerikson in https://github.com/reduxjs/react-redux/pull/1897Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.