Developer productivity is maximized when tooling removes constraints like configuration overhead, allowing for more creative problem-solving.
Nuxt 2's success with conventions like file-based routing and a module ecosystem informed the four key goals for Nuxt 3's evolution.
Nuxt 3 uses a configuration schema with inline JSDoc to automatically generate type definitions, markdown docs, and rich editor autocompletion.
Components placed in the `components` directory are automatically available throughout the application, complete with type-safe prop checking in the editor.
Nuxt 3 automatically registers plugins and imports exported functions from the `composables` directory, making them globally available without manual setup.
Nitro is a minimal, fast server engine designed for low cold-start times, cross-platform deployment, and optimized bundle sizes using code-splitting.
Create server API routes that are automatically typed, allowing the `useFetch` composable to provide end-to-end type safety from the backend to the frontend.
The build process creates a minimal, self-contained server output with code-splitting that dynamically loads only the necessary chunks for each request.
The team discusses handling bugs during the beta, ESM compatibility, the roadmap for component testing, and how to manage environment variables for deployment.
26:32Alexander Lichter
41:43Alexander Lichter
42:21Samuel Snopko
43:41Daniel Roe
44:31Rob Richardson
59:15Alvaro Saburido
44:11Mikhail Kuznetcov
49:00Marc Backes
Jobs that call for the skills explored in this talk.
doinstruct Software GmbH
Berlin, Germany
Speech Processing Solutions
Vienna, Austria