Vite Under a Lense
summary
Panel summarizes why Vite wins: it replaces webpack as Nuxt’s default so 95% of Nuxt users now use Vite, it standardizes on the rollup plugin API for single plugin surface, and teams build on Vitest, Vite Builder, VitePress and vite-node. Practical tips include avoiding barrel files to prevent huge imports, using glob/imports or V image tools for images, and never serving Vite dev server in production. Upcoming work highlights soft invalidation HMR to avoid retransforming unchanged modules and Vite 5 / Vitest 1.0 / VitePress 1.0 RC progress.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 3:54Vite’s growth factors
- 7:51Origin and pronunciation of Vite
- 8:12Vite project best practices
- 9:40Vite performance tips
- 11:03Vite plugin marketplace plans
- 13:52Contributing to Vite
- 15:41Vite accessibility improvements
- 19:25Dynamic image paths in Vite
- 21:12Vite configuration pitfalls
- 22:14Vite CORS issues
- 23:42Start contributing to Vite
- 25:35Latest VitePress updates
- 26:37Webpack to Vite migration
- 29:07Vite as production server
- 30:38TurboPack status and role
- 32:02Build steps vs no-build
- 36:21Vite for Node.js backends
- 38:05Testing watcher functions in Vite
- 39:33Vite module federation support
- 40:58Vite with Laravel
- 41:42VitePress future plans
- 44:34Vite with Bun
- 45:59New Vite features
- 49:55Closing remarks
related talks
38mHow vite changes the game for Vue and Web development
21mHow Vite Changes the Game for Vue and Web Developers
01h 19mVite Panel Discussion 2023
50mNuxt and Vite Core Teams LIVE panel
11h 49m42 talks about the tools and frameworks innovating in the Vite Ecosystem
43mInside a Pipeline: Demystifying Vite and Its Plugins
38mVite, a New Era of Frontend Tooling?
20mVite - The Next Generation Frontend Tooling