react-redux
9.3.1 · 27 Oct 2026MIT54.9M / weekRepositorynpmAtom feed
Upgrading react-redux From 0.3.0 to 0.9.0
11 releases in betweenevery note read
- 5
- changes to make
- 0
- advisories fixed
- 1
- new
- 6
- fixes
Before you upgrade
Tick each one off as you go- breaking0.8.0
- breaking0.7.0
- breaking0.7.0
- breaking0.7.0
- breaking0.5.0
Release by release
- new
Adds
ownPropsas an optional second parameter tomapStateToPropsandmapDispatchToProps: #59, #55. Note that, in order to get it, your functions have to declare it. In other words, they have to havefn.length > 1.
- new
- fixed
Fixes another issue where deleted props wouldn't get updated
- fixed
- fixed
Fixed child props failing to update when a prop is deleted
- fixed
- breaking
While this is very unlikely to break your app, components wrapped with
connect()now acceptstoreas an optional prop. So you may avoid using<Provider>after all, as long as you passstoremanually all the way down. (We don't suggest you to do this.) This is mostly useful for non-fully-React codebases and stubbing store for tests. If you use<Provider>, just keep using it and don't worry. (#33, #44)
- breaking
- breaking
Static property
DecoratedComponent=>WrappedComponent - breaking
Instance method
getUnferlyingRef()=>getWrappedInstance() - breaking
In addition, the wrapped instance is now available as
component.refs.wrappedInstance
- breaking
0.6.0nothing new or fixed in the note
- fixed
Fixes state not being updated in response to dispatches inside
componentWillMount
- fixed
- fixed
Fixes hot reloading actions and, hopefully, any
connect()parameter - fixed
Fixes a crash when specifying falsy, but not undefined,
connect()arguments
- fixed
1 other line we could not sort, mostly version bumps
- 0.4.0
<Connector>andprovide()are removed from the public API. Useconnect()and<Provider>instead.