forked from decentraland/kernel-legacy
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update react #133
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/react
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/react
branch
from
April 5, 2020 04:20
475ad11
to
ca1e67d
Compare
renovate
bot
changed the title
fix(deps): update dependency @types/react to v16.9.32
fix(deps): update react
Apr 5, 2020
renovate
bot
force-pushed
the
renovate/react
branch
7 times, most recently
from
April 13, 2020 03:34
e8658b7
to
3a4bb90
Compare
renovate
bot
force-pushed
the
renovate/react
branch
from
April 18, 2020 21:20
3a4bb90
to
f4e479d
Compare
renovate
bot
force-pushed
the
renovate/react
branch
3 times, most recently
from
April 27, 2020 21:58
59c3299
to
92c64da
Compare
renovate
bot
force-pushed
the
renovate/react
branch
2 times, most recently
from
May 11, 2020 01:54
ccf1cdb
to
8d8780f
Compare
renovate
bot
force-pushed
the
renovate/react
branch
from
May 19, 2020 19:53
8d8780f
to
03db4a1
Compare
renovate
bot
force-pushed
the
renovate/react
branch
2 times, most recently
from
June 10, 2020 09:21
933f729
to
6b7a03a
Compare
renovate
bot
force-pushed
the
renovate/react
branch
2 times, most recently
from
June 17, 2020 15:20
83c13b4
to
c876476
Compare
renovate
bot
force-pushed
the
renovate/react
branch
from
July 2, 2020 04:53
c876476
to
55969f7
Compare
renovate
bot
force-pushed
the
renovate/react
branch
from
August 26, 2020 11:04
55969f7
to
65a00c2
Compare
renovate
bot
force-pushed
the
renovate/react
branch
from
October 25, 2020 20:05
65a00c2
to
a28d1d7
Compare
renovate
bot
force-pushed
the
renovate/react
branch
from
November 28, 2020 18:04
a28d1d7
to
9bd9e80
Compare
renovate
bot
force-pushed
the
renovate/react
branch
from
December 11, 2020 20:03
9bd9e80
to
689c954
Compare
renovate
bot
force-pushed
the
renovate/react
branch
2 times, most recently
from
January 10, 2021 22:03
e0d83c9
to
46c40c2
Compare
renovate
bot
force-pushed
the
renovate/react
branch
from
January 23, 2021 11:55
46c40c2
to
dac73cf
Compare
renovate
bot
force-pushed
the
renovate/react
branch
from
February 9, 2021 15:50
dac73cf
to
4555d17
Compare
renovate
bot
force-pushed
the
renovate/react
branch
from
April 26, 2021 17:36
4555d17
to
803b53d
Compare
renovate
bot
force-pushed
the
renovate/react
branch
from
February 4, 2024 09:37
485fefe
to
0b1c7fe
Compare
renovate
bot
force-pushed
the
renovate/react
branch
2 times, most recently
from
February 26, 2024 21:22
073087e
to
55f720a
Compare
renovate
bot
force-pushed
the
renovate/react
branch
3 times, most recently
from
March 18, 2024 17:10
3d6f33d
to
26976c7
Compare
renovate
bot
force-pushed
the
renovate/react
branch
3 times, most recently
from
March 26, 2024 09:35
d766304
to
2e52322
Compare
renovate
bot
force-pushed
the
renovate/react
branch
2 times, most recently
from
April 21, 2024 07:39
efb7dab
to
e2e7a65
Compare
renovate
bot
force-pushed
the
renovate/react
branch
3 times, most recently
from
April 26, 2024 17:31
f44dff8
to
344b7b2
Compare
renovate
bot
force-pushed
the
renovate/react
branch
from
June 4, 2024 13:32
344b7b2
to
4a5b6f7
Compare
renovate
bot
force-pushed
the
renovate/react
branch
from
July 21, 2024 14:44
4a5b6f7
to
ad34b53
Compare
renovate
bot
force-pushed
the
renovate/react
branch
from
August 6, 2024 10:05
ad34b53
to
eadd50d
Compare
renovate
bot
force-pushed
the
renovate/react
branch
3 times, most recently
from
August 20, 2024 17:04
e157ddd
to
1f618d9
Compare
renovate
bot
force-pushed
the
renovate/react
branch
from
August 28, 2024 09:29
1f618d9
to
c53bead
Compare
renovate
bot
force-pushed
the
renovate/react
branch
from
September 16, 2024 11:18
c53bead
to
9683a78
Compare
renovate
bot
force-pushed
the
renovate/react
branch
2 times, most recently
from
September 27, 2024 18:52
efd45f6
to
6ec1e39
Compare
renovate
bot
force-pushed
the
renovate/react
branch
from
October 9, 2024 07:57
6ec1e39
to
48b7c0d
Compare
renovate
bot
force-pushed
the
renovate/react
branch
2 times, most recently
from
December 5, 2024 19:31
e88c4c9
to
c387007
Compare
renovate
bot
force-pushed
the
renovate/react
branch
from
December 9, 2024 20:26
c387007
to
f48693b
Compare
renovate
bot
force-pushed
the
renovate/react
branch
from
December 11, 2024 15:31
f48693b
to
d4cf9e2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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:
16.9.31
->16.14.62
16.9.6
->16.9.25
0.18.0
->0.28.9
7.1.7
->7.1.34
5.1.5
->5.1.20
5.1.3
->5.3.3
16.13.1
->16.14.0
2.1.0
->2.3.2
16.13.1
->16.14.0
0.25.1
->0.31.0
7.2.0
->7.2.9
Release Notes
facebook/react (react)
v16.14.0
Compare Source
React
brianzinn/react-babylonjs (react-babylonjs)
v2.3.2
Compare Source
v2.3.1
Compare Source
v2.3.0
Compare Source
v2.2.15
Compare Source
v2.2.14
Compare Source
v2.2.13
Compare Source
v2.2.12
Compare Source
v2.2.11
Compare Source
v2.2.10
Compare Source
v2.2.9
Compare Source
v2.2.8
Compare Source
v2.2.7
Compare Source
v2.2.6
Compare Source
v2.2.5
Compare Source
v2.2.4
Compare Source
v2.2.3
Compare Source
v2.2.2
Compare Source
react-babylonjs
context. Fixes #60. - @brianzinnreact-spring
(and 14 other unused dependencies). #69 - @brianzinnonPointerEnterObservable
. #55 - @brianzinnv2.2.1
Compare Source
v2.2.0
Compare Source
facebook/react (react-reconciler)
v0.31.0
Compare Source
v0.29.2
Compare Source
v0.29.1
Compare Source
reduxjs/react-redux (react-redux)
v7.2.9
Compare Source
This patch release updates the rarely-used
areStatesEqual
option forconnect
to now pass throughownProps
for additional use in determining which pieces of state to compare if desired.The new signature is:
What's Changed
Full Changelog: reduxjs/react-redux@v7.2.8...v7.2.9
v7.2.8
Compare Source
This release fixes a bug in the 7.x branch that caused
<Provider>
to unsubscribe and stop updating completely when used inside of React 18's<StrictMode>
. The new "strict effects" behavior double-mounts components, and the subscription needed to be set up inside of auseLayoutEffect
instead of auseMemo
. This was previously fixed as part of v8 development, and we've backported it.Note: If you are now using React 18, we strongly recommend using the React-Redux v8 beta instead of v7.x!. v8 has been rewritten internally to work correctly with React 18's Concurrent Rendering capabilities. React-Redux v7 will run and generally work okay with existing code, but may have rendering issues if you start using Concurrent Rendering capabilities in your code.
Now that React 18 is out, we plan to finalize React-Redux v8 and release it live within the next couple weeks. Per an update yesterday in the "v8 roadmap" thread, React-Redux v8 will be updated in the next couple days to ensure support for React 16.8+ as part of the next beta release. We would really appreciate final feedback on using React-Redux v8 beta with React 18 before we publish the final version.
Full Changelog: reduxjs/react-redux@v7.2.7...v7.2.8
v7.2.7
Compare Source
This release updates React-Redux v7's peer dependencies to accept React 18 as a valid version, only to avoid installation errors caused by NPM's "install all the peer deps and error if they don't match" behavior.
Note: If you are now using React 18, we strongly recommend using the React-Redux v8 beta instead of v7.x!. v8 has been rewritten internally to work correctly with React 18's Concurrent Rendering capabilities. React-Redux v7 will run and generally work okay with existing code, but may have rendering issues if you start using Concurrent Rendering capabilities in your code.
Now that React 18 is out, we plan to finalize React-Redux v8 and release it live within the next couple weeks. We would really appreciate final feedback on using React-Redux v8 beta with React 18 before we publish the final version.
v7.2.6
Compare Source
Just a quick fix for a Yarn install warning. Sorry about the noise!
Changes
workspaces
from our package.json to silence a Yarn warning (@timdorr)v7.2.5
Compare Source
This release shrinks the size of our internal
Subscription
class, and updatesuseSelector
to avoid an unnecessary selector call on mount.Changes
Subscription Size Refactor
Our internal
Subscription
implementation has been written as a class ever since it was added in v5. By rewriting it as a closure factory, we were able to shave a few bytes off the final bundle size.useSelector
Mount OptimizationA user noticed that
useSelector
had never been given an early "bail out if the root state is the same" check to match howconnect
works. This resulted in a usually-unnecessary second call to the provided selector on mount. We've added that check.Entry Point Consolidation
We've consolidated the list of exported public APIs into a single file, and both the
index.js
andalternate-renderers.js
entry points now re-export everything from that file. No meaningful change here, just shuffling lines of code around for consistency.Other Updates
React-Redux v8 and React 18 Development
With the announcement of React 18, we've been working with the React team to plan our migration path to keep React-Redux fully compatible with React's upcoming features.
We've already migrated the React-Redux main development branch to TypeScript, and are prototyping compatibility implementation updates. We'd appreciate any assistance from the community in testing out these changes so that we can ensure React-Redux works great for everyone when React 18 is ready!
Internal Tooling Updates
Our
master
branch now uses Yarn v2 for package management, is built with TypeScript, and we've made CI updates to test against multiple TS versions.The
7.x
branch has also been updated to use Yarn v2 for consistency.These only affect contributors to the React-Redux package itself.
Changelog
v7.2.4
Compare Source
This release drops our dependency on the core
redux
package by inliningbindActionCreators
, and tweaksuseSelector
to ensure that selectors aren't run an extra time while re-rendering.Changelog
Redux Dependency Removal
React-Redux has always imported the
bindActionCreators
utility from the coreredux
package for use inconnect
. However, that meant that we had to have a peer dependency onredux
, and this was the only reason we actually required thatredux
be installed. This became more annoying with the arrival of Redux Toolkit, which has its own dependency onredux
internally, and thus users typically saw peer dependency warnings saying that "redux
isn't listed as a dependency in your app".Code reuse across separate packages is a great thing, but sometimes the right thing to do is duplicate code. So, we've inlined
bindActionCreators
directly into React-Redux, and we've completely dropped the dependency on Redux. This means that React-Redux will no longer produce a peerDep warning when used with Redux Toolkit, and<Provider>
andconnect
really only need a Redux-store-compatible value to work right.useSelector
FixesUsers reported that
useSelector
was re-running selector functions again unnecessarily while rendering after a dispatch. We've tweaked the logic to ensure that doesn't happen.useSelector
also now has checks in development to ensure thatselector
andequalityFn
are functions.Changes
v7.2.3
Compare Source
This release improves behavior in
useSelector
by returning the existing reference if the newly returned selector result passes the equality check, and adds a hard dependency on the@types/react-redux
package to ensure TS users always have the typedefs installed.Changes
useSelector
Results ReuseIssue #1654 reported that
useSelector
was returning new references from a selector even if the equality comparison function returnedtrue
. This is because the equality check was only ever being performed during the action dispatch process.We now run the equality comparison against the value calculated by the selector while rendering, and return the existing reference for consistency if the old and new values are considered equal. This should improve some cases where further derived values where being recalculated unnecessarily.
TS Types Now Included
React-Redux has always been written in plain JS, and the typedefs maintained by the community in DefinitelyTyped. We plan on eventually rewriting the library in TypeScript in a future React-Redux v8 release, but until then the types can stay in DT.
However, having to always manually install
@types/react-redux
is annoying, and some users have gotten confused by that. This release adds a hard dependency on@types/react-redux
, so that if you installreact-redux
, you automatically get the types as well. This should simplify the process for TS users.Docs Updates
We've made several docs updates recently:
We are currently working on a new React-Redux tutorial that will teach the React-Redux hooks as the primary approach, based on the "UI and React" page in the Redux docs "Fundamentals" tutorial.
Changelog
v7.2.2
Compare Source
This release allows you to use React Redux with React 17 without a warning when installing. That's about it.
Changes
v7.2.1
Compare Source
This release improves
useSelector
value display in the React DevTools, fixes a potential race condition, and fixes a couple additional minor issues.useSelector
DevTools DisplayThe React DevTools normally show custom hooks with their inspected name (such as "Selector" for
useSelector
), and any calls to core hooks inside. This is not always informative, so React has theuseDebugValue
hook to allow custom hooks to specify what value should be shown instead.useSelector
now callsuseDebugValue
to specifically show the current selected value instead of its internal hooks usage.Bug Fixes
This release has a few different bug fixes:
reactReduxForwardedRef
to avoid a rare situation where someone else might be passing down a field namedforwardedRef
useSelector
error messageChanges
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 is behind base branch, 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 was generated by Mend Renovate. View the repository job log.