Developer Experience with Nuxt
summary
Nuxt 3 claims much faster feedback by switching to Vite HMR and shipping Nitro backend reloads so client, server and API edits apply without restarts. Conventions like file routing and components auto-imports cut boilerplate and are fully typed, not just promised. To fix lost transparency, a Vit plugin inspect and a built Nuxt Devtools with embedded VS Code server let developers see transforms, component graphs, runtime hooks and reactive config. The Devtools demo mostly works though some features remain early preview.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:53Responsiveness
- 3:09Common Practices
- 4:31Conventions
- 6:22Ecosystem
- 7:00One problem - Transparency
- 7:43vite-plugin-inspect
related talks
33mNew Developer Experiences with Nuxt 3
26mOptimising Developer Experience with Nuxt 3
40mNow, and the Future of Nuxt DevTools
38mHow vite changes the game for Vue and Web development
20mVite - The Next Generation Frontend Tooling
33mNuxt's Hidden Treasures: 8 Gems Every Nuxt Dev Should Know!
26mVue & Vite Devtools
15mNew Ways to Vue
