Señors at Scale - Software Engineering & Tech Leadership · Dan Neciu

Nuxt at Scale with Daniel Roe

·54 min·3 clips

Nuxt.com cut JavaScript by 66% by extracting data-fetching and code-sample logic.

1. Señors at Scale speaks with Daniel Roe about Nuxt, Vue, serverless deployment, and scaling full-stack apps. 2. Daniel Roe leads the Nuxt core team at Vercel and works with companies on architecture, serverless strategy, and full-stack apps. 3. The episode asks how Nuxt stays simple while serving marketing sites, dashboards, and large-scale production systems. 4. Daniel says he first found Vue through Laracasts and Geoffrey Way while running a small creative agency. 5. He describes building WordPress themes, wanting better practices, and learning from Laravel, Roots, and 12-factor ideas. 6. He says Vue spread through the Laravel world because it could be dropped in as a script tag and make rendered HTML interactive. 7. Daniel explains that he chose Nuxt after wanting to server-render Vue code for agency projects. 8. He says Nuxt was already popular when he joined, alongside frameworks like Quasar and Gridsome. 9. Daniel credits Sebastian, Alexander Chapan, and early contributor Parza for creating and growing Nuxt before his core-team work. 10. He says the Nuxt community welcomed him on Discord, answered his questions, and reviewed his early pull requests. 11. Daniel argues that open source works best when developers are their own target audience. 12. He says he often debugged Nuxt by adding console logs, grepping the repo, and tracing the exact line setting a value. 13. He identifies re-implementing fetch logic as a major mistake because Nuxt data helpers are context-aware per request. 14. He says server rendering can bottleneck when teams repeatedly fetch the same CMS or database data on every request. 15. Daniel recommends the simplest rendering strategy first, especially static pre-rendering when pages can be reused for thousands of requests. 16. He says Nuxt route rules can mix pre-rendered marketing pages with per-request dashboards and even pages with no JavaScript. 17. Daniel explains that Nuxt 3 came from a rewrite driven by Vue major changes, Webpack changes, and Vite. 18. He says Nitro was extracted for universal deployment targets like Cloudflare Workers, Bun, standalone Docker images, and Nuxt 3 and can also power tools like SolidStart and TanStackStart. 19. The conversation stays practical and explanatory, with Daniel answering architecture questions directly and using examples from Nuxt.com, Glovo, and enterprise layering. 20. Developers building Vue apps, Nuxt teams, and engineers interested in deployment and rendering tradeoffs will get the most from this episode.

As heard by us

A practical look at Nuxt performance, with a real Nuxt.com example and enough technical detail to stay useful.

The episode stays tightly focused on how JavaScript behaves under load. Daniel walks through bundlers, tree shaking, lazy loading, and a few small choices that help an app stay fast.

Read the full review in PlayNext →

Why you'd press play

You want the Nuxt decisions behind faster apps, not the marketing version.

Read the full recommendation in PlayNext →

Listen to the show on

Apple Podcasts Spotify

Play clips from this episode More from Señors at Scale - Software Engineering & Tech Leadership