Managing a Large in Place Migration to Nuxt js
summary
A large Rails + Vue app with custom server‑side rendering migrates in place to Nuxt.js by matching directory structure and core libraries, keeping Apollo/GraphQL and auth intact, and splitting work into prep then cutover phases so commits stay small; a small team coordinates while 80 contributors keep working across 14,000 commits; the actual switch is swapping in the Nuxt.js bundle renderer and a boot hook limits what pages compile to fix performance.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 0:27Background of Problem
- 2:27Nuxt js
- 4:14Make it Easier
- 5:36Deploy Smaller Chunks
- 6:39Prep
- 7:04Cutover
- 7:15Done
related talks
21mHow to enable large scale collaboration between disciplines using Nuxt
20mHow to Seamlessly Migrate a Large Codebase to Vue 3
35mHow to migrate a large app to Vue 3
31m'I need it yesterday!' - The secret story of MDS
47mReal and Scalable Applications with Nuxt, Vuex and Typescript
26mMigrating a big old codebase to Vue 3: what I'm excited about
31mNailing It with Nuxt 3 - Inside and Out
44mFrom Legacy to Vue.js