Next.js App Router

[eugeniosegala]

Hello!

I'm using Redux RTK query on the server with Next.js, following the official doc.

I'm currently in the process of considering migrating my application to the "App Router" paradigm, however, I noticed that Redux RTK query is not compatible with that configuration at this time.

I started playing a bit with the new App Router feature and I noticed some limitations around accessing the full request object and other similar things. In general, it looks like what you can do from a server side prospective, it's more limited than before.

I was wondering, what is the position of the Redux team about this? It seems the App Router will become the standard at some point?

I'm happy to help figuring this out, perhaps we can reach out to the Next.js team and find a way to fix the above?

Thanks!

[markerikson]

Can you clarify the specific question you're asking?

Short answer is that Next and React are both looking to move more things to the server. RTK Query is not as potentially relevant in that scenario. But also there's a lot of technical complications towards potentially integrating RTKQ into a server component environment. See https://phryneas.de/react-server-components-controversy for some details.

[eugeniosegala]

My question is:

How can I use the "RTK Query Server Side Rendering feature" in combination with the Next JS "App Router" feature?

It can be used with the getServerSideProps approach but it looks like it's not possible to use it with the new way Next JS decided to go forward.

I think there is still value in having RTK Query server side, mostly because you can:

• Be compliant with the "Progressive enhancement" pattern
• Fetch data server-side and rehydrate client-side
• Centralised source of truth for your data
• and more...

What would be the alternative at the moment to achieve similar results using Next.js App Router?

If there is appetite to make RTK work with the App Router, I'm happy to be involved.

I will read the article you shared :)

[markerikson]

We don't have a valid solution for that right now that I know of. Based on Lenz's article, it seems that there's some technical pieces that simply don't exist on the React side.

We're certainly open and interested in potential solutions, but tbh right now all my Redux attention is focused on shipping RTK 2.0. Per my comment at #958 (comment) , we're going to defer all major RTKQ changes for after 2.0.

We'd definitely welcome help (both ideas and contributions), just setting expectations that this is not an immediate priority for us and I honestly don't know if it's technically feasible.