Accessing store from NextJs middleware

[robertodilillo]

Is your feature request related to a problem? Please describe. Currently there is no support to use state in middleware functions

Describe the solution you'd like NextJs 12 allows middleware. would be good

Describe alternatives you've considered the only alternative is to repeat the middleware logic in any index page or have it in the _app file which would exclude the automatic static optimization

Additional context here s an example

import { NextResponse } from 'next/server';
import { nextStore } from '@store/store';

export const middleware = nextStore.middleware((store) => async ({ req, query, res }) => {
	const { tick } = store.getState();
	console.log(tick);
	return NextResponse.next();
});

[zhangwei900808]

refresh token need!

[HamAndRock]

I actually digged into middlewares, and from what I saw they are only used for responses manipulation. So you are not able to pass any props to the code => meaning that you cannot return the new redux state. The only workaround that I kinda came with would be to use cookies for this, but that seems like an overkill...

[bjoluc]

So you are not able to pass any props to the code => meaning that you cannot return the new redux state.

Valid point. I was in a rather niche situation recently though where just having a next-redux-wrapper-created store instance in a middleware would have been enough, since I was using my next-redux-cookie-wrapper thingy (which, I guess, is what @bryantobing12 and @zhangwei900808 are doing too).

[gmonitoring]

Any updates on this? I tried using getStaticProps internally in middleware and it looks like a possible solution. But the state after hydration remains default