Make applyMiddleware optionally support a more "Nodeish" API

[dtothefp]

Do you want to request a feature or report a bug?
feature

What is the current behavior?

function someMiddleware(opts) {
  return ({ dispatch, getState }) => next => action => //do stuff
}

would be nice and easier to understand for those used to Node/Express/Koa to do

function someMiddleware(opts) {
  return ({ dispatch, getState }) => (action, next) => //do stuff & call `next()`
}

Would be trivial to do and could be made backwards compatible for current middleware style by checking middleware function argument length

const [last] = chain.slice(-1);
const rest = chain.slice(0, -1);
const wrap = (fn, next) => {
  return fn.length === 2 ? (action) => fn(action, next) : fn(next);
};

const newDispatch = rest.reduceRight((next, fn) => wrap(fn, next), wrap(last, store.dispatch));

Sorry if similar issues have been previously posted (I didn't find any in my search) and wondering if you'd be open to a PR?

[markerikson]

Yeah, variations on this have been discussed previously, and turned down. See #534 , #922, and #1744 for prior discussion.

[dtothefp]

😢 seems like being able to provide this API while at the same time supporting next => action through arguments check is best of both worlds ¯\_(ツ)_/¯

[jimbolla]

You could write your own applyMiddleware, as it's only about 20 lines of code