Open
Conversation
Snyk has created this PR to upgrade react-redux from 6.0.0 to 6.0.1. See this package in npm: https://www.npmjs.com/package/react-redux See this project in Snyk: https://app.snyk.io/org/lethu96/project/e5d542a2-8d74-42d7-a73d-89e6a33bc134?utm_source=github&utm_medium=referral&page=upgrade-pr
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Snyk has created this PR to upgrade react-redux from 6.0.0 to 6.0.1.
ℹ️ 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.
Release notes
Package name: react-redux
-
6.0.1 - 2019-02-20
- Fix for circular component object structures, such as Emotion styled components. (#1122 by @ Andarist)
- Minor optimization: remove conditional (#1131 by @ ericanderson)
- Ensure that component
- react-hot-loader compatibility (#1168/#1137 by @ theKashey)
- Upgrade to react-is v16.7.0 (#1174 by @ nobezawa)
-
6.0.0 - 2018-12-05
-
-
- Use React.createContext() (#1000 by @ cellog)
- Use Prettier (#1071 by @ NMinhNguyen)
- Only run isValidElementType in development builds (#1069 by @ alexreardon)
- Treat
- Ensure connectAdvanced only re-renders if derived props change (#1079 by @ epeli and @ markerikson)
from react-redux GitHub release notesThis is a minor release with support for react-hot-loader and a few small bug fixes for edge cases.
While you're here, please stop by #1177 to see our roadmap for the next versions of React Redux. We are aware that performance is not so hot in 6.0. Short version: We put too much traffic on React's context API, which isn't really designed for high levels of reads and writes. We're looking to reduce that load and get performance back on track in a minor release, so there won't be backwards compatibility concerns. We have a new extensive benchmark suite to keep us on track and ensure we're not regressing on speed in the future.
And yes, we know about Hooks. Check out #1179.
Changes
contextprop really contains a React context (#1134 by @ casdevs)🎉 This is our first big release supporting the new Context API added in React 16.4!
As such, we now require React 16.4 or higher. Make sure to update your version when updating to this release.
This work has been mostly lead by @ cellog and @ markerikson, with special guest appearances by yours truly and a whole cast of helpful reviewers.
Breaking Changes
The
withRefoption toconnecthas been replaced withforwardRef. If{forwardRef : true}has been passed toconnect, adding a ref to the connected wrapper component will actually return the instance of the wrapped component.Passing
storeas a prop to a connected component is no longer supported. Instead, you may pass a customcontext={MyContext}prop to both<Provider>and<ConnectedComponent>. You may also pass{context : MyContext}as an option toconnect.Behavior Changes
Any library that attempts to access the store instance out of legacy context will break, because we now put the store state into a
<Context.Provider>instead. Examples of this includeconnected-react-routerandreact-redux-subspace. (The current implementation does also put the store itself into that same context. While accessing the store in context is not part of our public API, we will still try to make it possible for other libraries to access it, with the understanding that this could break at any time.)Also, there is a behavior change around dispatching actions in constructors /
componentWillMount. Previously, dispatching in a parent component's constructor would cause its children to immediately use the updated state as they mounted, because each component read from the store individually. In version 6, all components read the same current store state value from context, which means the tree will be consistent and not have "tearing". This is an improvement overall, but there may be applications that relied on the existing behavior.Changes
nullas a valid plain object prototype inisPlainObject()(#1075 by @ rgrove)Commit messages
Package name: react-redux
Compare
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:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs