The build tool for the web. It's pronounced /vit/ like Veet! | brought to you by @voidzerodev and the community - join us on Discord: chat.vite.dev
- Tweets 1,950
- Following 186
- Followers 140,988
- Likes 4,331
ALT Anthony's Speaker Card for ViteConf 2025. Shows a headshot, his full name, that he is part of the Vite Core Team and his talk title "Vite Devtools"
ALT Speaker card of Johannes Schickling for ViteConf 2025. It contains his Job Title, "Founder of Prisma", and his talk title "Native-Grade Web Apps with Local-First Data"
ALT Speaker card of Jessica Janiuk from ViteConf 2025. It mentions that the is on the Angular Framework Team and her talk is about "Angular and Vite"
ALT Speaker Card of Matt Biilmann, CEO at Netlify. His Talk: From DX to AX
ALT Speaker Card of Evan You showing "ViteConf 2025", his name, the title "Creator of Vite" and his talk title "Vite: Beyond a Build Tool"
![Picture of VS Code with an open minimal Vite project. The Vite config only sets `experimental.enableNativePlugin` to "resolver" with a comment saying "// or true, either is necessary", and "resolve.tsconfigPaths" to true.
The tsconfig.json has `compilerOptions.paths` set to `{ "app/*": ["./src/app/*"]`. Eventually, the path resolution is used automatically (wtih autocomplete too!) in src/main.ts when using `import { App } from "app/my-app.ts`, instead of `import { App } from "./src/app/my-app.ts"`!](/pic/orig/media%2FGvk6gLyXkAAIllL.jpg)
ALT Picture of VS Code with an open minimal Vite project. The Vite config only sets `experimental.enableNativePlugin` to "resolver" with a comment saying "// or true, either is necessary", and "resolve.tsconfigPaths" to true. The tsconfig.json has `compilerOptions.paths` set to `{ "app/*": ["./src/app/*"]`. Eventually, the path resolution is used automatically (wtih autocomplete too!) in src/main.ts when using `import { App } from "app/my-app.ts`, instead of `import { App } from "./src/app/my-app.ts"`!