Create new npm release

[tony-scio]

Feature Request

There are a lot of good updates since the last npm release over 2 years ago. v2.3.0...master

It'd be really great if whoever has access could cut a new release.

[FernandoChu]

Second this, mainly the changes to the types definitions would have helped me a lot.

[eaglus]

@timdorr @gaearon @aikoven Please publish a latest version of this package. We use our private npm package based on latest master of redux-think, and dream to have a latest official version, and drop out private package

[gaearon]

@tony-scio Do you want to cut npm releases? I'm happy to add as an owner.

[markerikson]

FWIW, the last time Tim and I chatted about this, he was concerned that the current types may not be sufficiently correct or something along those lines. Tim, can you clarify what those concerns are atm?

[timdorr]

Yes, I'm primarily concerned that we're using a number of overloads to apply the thunk types, rather than preferring the middleware approach. This means that the Dispatch and bindActionCreators types get overridden if the module is included, even if it's not used.

This also creates a problem for using multiple middlewares on the same store, where they may get clobbered by this overload. I'm not sure of the priority order on overloads vs. directly applied types, but that uncertainty makes me wary.

For reference, here are the PRs with type changes since 2.3.0:

#216
#219
#224
#243
#255
#260
#263
#278

I have some regret about merging in #224 and #278, since they add the overloads. They also tie to the specific types we have in Redux 4.x, and will break under 5.0.

[tony-scio]

@gaearon I'm probably not yet well qualified to be responsible for redux-thunk releases as I haven't developed in this library. I'm just a consumer of the library who is still very much looking forward to the next release.

[flymoondust]

I'm also looking forward the next release。My company has standard for picking third part library,Now for 2 years no new release, I may be forced to pick alternative library, but I don't know any other library.

[timdorr]

Just keep in mind the only thing that has changed in that time is the build system and the TypeScript types. The code of the actual middleware hasn't changed in 4 years, and that was only to add extraArgument.

[tony-scio]

@timdorr apologies for the naive question, but why not make a release branch and, on it, back out the 2 commits you mentioned that you regret? One of the other type improvements would have saved me a prod bug. Seems unfortunate to hold them back from users.

[gregtatum]

Just chiming in to say that I've put lots of hours over the years into trying to type thunks in both Flow types and TypeScript, so having some kind of type-safe solution that is type-correct for connected components, even if not ergonomic would be a huge windfall. I'm more concerned about catching bugs, rather than having an ergonomic API. This typing doesn't appear to be a solved problem with any kind of official recommendation, even if it's a "this is not great, but it works".

That said, thanks for the maintenance work, I find redux-thunk essential for the apps I maintain.

[GLObus303]

Hey, any plans on releasing the fixes?