Hi @sweet trellis. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
#redux toolkit with serverside rendering nextjs 14 using app Router
frank ridgeBOT
Server-Side Rendering (SSR) in Next.js allows you to render pages dynamically on the server. This is particularly useful for pages where the rendered data needs to be unique on every request, such as checking authentication or looking at the location of an incoming request.
In Next.js, you can use SSR to render pages on each request. You can learn more about this in the Next.js documentation on Server-side Rendering (SSR) (https://nextjs.org/docs/pages/building-your-application/rendering/server-side-rendering).
On Vercel, you can server-render Next.js applications in either the Node.js runtime (default) with Serverless Functions (https://vercel.com/docs/functions/serverless-functions) or the Edge runtime with Edge Functions (https://vercel.com/docs/functions/edge-functions). This allows you to pick the best rendering strategy on a per-page basis.
To summarize, SSR with Next.js on Vercel:
- Scales to zero when not in use
- Scales automatically with traffic increases
- Has zero-configuration support for
Cache-Controlheaders (https://vercel.com/docs/edge-network/caching), includingstale-while-revalidate - Framework-aware infrastructure enables switching rendering between Edge/Node.js runtimes
You can learn more about SSR on Vercel in the Vercel documentation (https://vercel.com/docs/frameworks/nextjs).
As for using Redux Toolkit with SSR in Next.js, the provided extracts do not contain specific information on this topic. However, Redux Toolkit can generally be used with Next.js and its SSR feature. You would typically wrap your pages with a Redux provider and use Redux Toolkit actions and reducers to manage state on the server side before rendering.