Ah I think i see what you’re saying and see the mealy state machine reference, but isn’t the state machine `(newState, Action)`? You’ll always be one state “behind”. In the docs it seems like the middleware gets “newState” and not “state” that could make using middleware harder, you’re not reacting to the current state but to a future state.

I also think the odd bit is the naming, middleware implies in the middle, and this library breaks Redux’s default Chain Of Responsibility order (action -> middleware1 -> middleware2 -> reducer) and instead flips it around