redux

5.0.1 · 23 Dec 2023MIT62.6M / weekRepository Homepage npm Atom feed

Upgrading redux From 4.1.2 to 4.2.1

Same major only

2 releases in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 4.1.2Latest5.0.1

Tick each one off as you go

This release marks the original createStore API as @deprecated to encourage users to migrate to Redux Toolkit, and adds a new legacy_createStore API as an alias without the deprecation warning.
deprecated4.2.0
We already had a package rename from redux-starter-kit to @reduxjs/toolkit, and all of our docs and tutorials have pointed to it for the last three years. I don't want to put users through another whiplash package transition for no real benefit
deprecated4.2.0
Merging or rearranging our packages would effectively require merging all of the Redux repos into a single monorepo. That would require hundreds of hours of effort from us maintainers, including needing to somehow merge all of our docs sites together. We don't have the time to do that.
deprecated4.2.0
Mark createStore as deprecated, and add legacy_createStore alias
deprecated4.2.0

6 other lines we could not sort, mostly version bumps

Remove minified check
4.2.1
RTK provides a vastly improved Redux usage experience, with APIs that simplify standard usage patterns and eliminate common bugs like accidental mutations
4.2.0
I don't want to add runtime warnings that would be really annoying
4.2.0
Follow our suggestion to switch over to Redux Toolkit and configureStore
4.2.0
Do nothing. It's just a visual strikethrough, and it doesn't affect how your code behaves. Ignore it.
4.2.0
Switch to using the legacy_createStore API that is now exported, which is the exact same function but with no @deprecation tag. The simplest option is to do an aliased import rename:
4.2.0

npm install redux@4.2.1

Reading 4.2.1's manifest…

Check against your package.json

Which of your other dependencies stand in the way of 4.2.1. Read once, not stored.