@timdorr timdorr released this Apr 17, 2018 · 48 commits to master since this release

Assets 2

Redux 4 is here! πŸŽ‰

If you're a React user, this is going to be a lot like going from 15 to 16. Not a lot of user-facing changes, but some interesting improvements under the hood.

The major changes (#1342) are around our TypeScript definitions, bundled CommonJS and ES builds, throwing if you subscribe or getState from a reducer, and a bunch of other smaller things. The full changes are listed below.

Enjoy!

Changes

Pre-release

@timdorr timdorr released this Apr 10, 2018 · 57 commits to master since this release

Assets 2

npm install redux@next

There haven't been any big complaints with the previous beta, so it's time to graduate to a release candidate. Please give this a try in your applications and let us know if you see any issues. If we're all clear, I'll get 4.0 released in the next week!

Changes

Pre-release

@timdorr timdorr released this Feb 15, 2018 · 95 commits to master since this release

Assets 2

npm install redux@next

Another beta release to test our TypeScript typings. Feedback is greatly appreciated!

Changes

Pre-release

@timdorr timdorr released this Nov 16, 2017 · 145 commits to master since this release

Assets 2

It's time to bump the major version on Redux! πŸŽ‰

This is the first beta release of 4.0.0. Despite the version bump, the changes are relatively minor. Most of it was covered in the 4.0 tracking issue: #1342.

The largest amount of work was done with our Typescript definitions. They have been completely overhauled, so they should work better and take advantage of all the new stuff in TS 2.x.

The other big change is we are now bundling our CommonJS and ES builds like React has done recently. This means direct, private imports (import createStore from 'redux/lib/createStore') will no longer work. This ensures our modules are maintaining a consistent contract with your apps and that any reorganization we choose to do internally has no effect on your usage of Redux.

We've also tightened up some behavior quirks and dropped support for IE < 11. The vast majority of apps should require no changes. But we will run through a standard RC process to gradually release this out to the world and ensure no big headaches for everyone during the holiday season.

Enjoy!

Changes

@timdorr timdorr released this Jul 13, 2017 · 283 commits to master since this release

Assets 2

Changes

@timdorr timdorr released this Jun 26, 2017 · 293 commits to master since this release

Assets 2

This reverts the console.error on bindActionCreators() coming from #2279.

While well-intentioned, when star importing all exports from a module (import * as actions from './actions'), transpilation by Babel defaults to adding a default and __esModule property to the import, which are not functions. While it can be disabled, this isn't common to do and leads to a lot of confusion. So, we're reverting the change.

Thanks for the feedback from everyone and the civility and healthy discourse on the issue!

@timdorr timdorr released this Jun 17, 2017 · 302 commits to master since this release

Assets 2

Another long break!

Oh, hey! I didn't see you sitting there. You look bored. How about a Redux release to spice things up?

Not a huge set of changes to report here. The biggest change, and the reason for the minor bump, is the UMD build is now done via Rollup. One big advantage is more readable code in the bundle. Rollup does "scope hoisting", which is a fancy term for putting every module at the top level of the file. Other than a surrounding IIFE, all of the code in Redux all lives together. You can compare the two here:

Rollup UMD build
vs
Webpack UMD build

There is also a cost savings of 30,811 vs 26,880 bytes, and 6,999 vs 5,995 bytes minified. Redux is already a small library, and this helps shave some extra bytes for our UMD users.

One thing to note is that Webpack has introduced it's own scope hoisting feature in 3.0 beta. So, this isn't intended as an indictment of Webpack. You should continue to use it in your own apps. The adage of "Webpack is for apps, Rollup is for libraries" definitely holds true. It still has a superior developer experience with hot module reloading and webpack-dev-server. But use whatever makes sense for your project, not just whatever we use. πŸ˜„

We're also looking at applying this to the NPM bundle. The main motivation is again more readable code in your bundles. Instead of transpilation oddities from Babel, you will end up with a single clean file, which should be easier to read through and debug. It's currently scheduled for the big, mythical 4.0 release and you can follow along in #2358

Changes

@timdorr timdorr released this Sep 4, 2016 · 611 commits to master since this release

Assets 2

Hey, it's been a while!

How's everyone doing? Enjoying your summer (or winter for the Southern Hemisphere folks)?

This is a bugfix release for Redux. We're working towards a 4.0 with more substantial changes. Please see #1342 to pitch in!

Dan also ported all the examples (except the universal one) in #1883 to use the excellent Create React App. This means the changes in #1800 have been lost. If you'd like to help out, we would love PRs on the examples to modernize and clean them up.

Changes

  • Updated symbol-observable to 1.0.2 (#1663 and #1877)
  • Added a Redux logo (#1671)
  • Replace es3ify with Babel ES3 transforms (#1688)
  • Run tests on Node 6 (#1673)
  • Optimize one function case in compose (#1701)
  • Check ES3 syntax compatibility (#1720)
  • TypeScript: preloadedState is optional (#1806)
  • Add a warning for undefined properties passed to combineReducers (#1789)
  • Add module entry point for webpack 2 (#1871)
  • TypeScript: Improve typings for compose function (#1868)

@gaearon gaearon released this Apr 24, 2016 · 716 commits to master since this release

Assets 2
  • Enforces a newer version of symbol-observable that works in IE8 (#1659)

@gaearon gaearon released this Apr 20, 2016 · 723 commits to master since this release

Assets 2
  • Fixes a regression introduced in 3.5.0 that caused dispatch to not be available while middleware is initializing. (#1644, #1647)