Incrementally migrating to Next.js from a client-side-only app @VercelHQ
Incrementally migrating to Next.js from a client-side-only app @VercelHQ
Uploaded November 2024 | Updated September 2026, 1 week ago
The long and winding road: CSR to static export to SSG

Nick Hess recaps Peloton’s multi-year migration to Next.js from a client-side-only app in a large monorepo, leading to improved page performance, productivity, and streamlined architecture.

00:00 - Intro
2:21 - Migration
10:23 - Results

Read the full Next.js Conf 2024 recap: vercel.com/blog/recap-next-js-conf-2024

Deploy your Next.js app with Vercel: vercel.com/new
Incrementally migrating to Next.js from a client-side-only appMulti-Step (Agentic) Generation with the AI SDKCTO panel: Internal apps and agents in production - Ship 26 NYCHow to Use GitHub v0Vercel Ship 2024 Keynote Feature: Toolbar & Feature FlagsBringing React Components to AIVercel Ship 2025 workshop: Anatomy of a fast site (Matt Jared)Build and deploy a Slack Agent to Vercel - Ship 26 NYC WorkshopAMA: From Briefs to Prototypes: Build at the Speed of Trustv0 Power Hour: Lets ship an agentv0 Power Hour: Let’s Build an AgentBuild a fullstack app in 7 minutes with v0 (Figma to code)
Vercel |

Incrementally migrating to Next.js from a client-side-only app

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER