Developers' Mistakes with Nuxt – Daniel Roe
summary
Common mistakes: overcomplicating too early by wiring global browser-style state into server-rendered pages, and assuming client code maps directly to multiuser server execution. Advice includes initializing state per request, avoiding shared globals that leak between users, and using Nuxt lifecycle and server-aware data hooks to keep renders fresh. The concrete claim is simple: simpler patterns first, then only introduce complexity when profiling or a clear multi-request bug proves it necessary.
AI-written summary · about
related talks
31mCommon Mistakes in Vue and Nuxt and How to Avoid Them
08mUnderstand the hard parts of Nuxt
32mUnderstand the hard parts of Nuxt
38mLarge Scale Nuxt Architecture
19mPatterns for Large Scale Vue.js Applications
25mCommon Mistakes in Vue.js and How to Avoid Them
33mNuxt's Hidden Treasures: 8 Gems Every Nuxt Dev Should Know!
22mWays to architecture your vue/nuxt app