?raw import
\n\n
\n
\n \n ![\"vite](\"https://vite.dev/vite-dark.svg\")
\n
\n
\n
\n
\n ![\"npm](\"https://img.shields.io/npm/v/vite.svg\")
\n ![\"node](\"https://img.shields.io/node/v/vite.svg\")
\n ![\"build](\"https://github.com/vitejs/vite/actions/workflows/ci.yml/badge.svg?branch=main\"){kind=icon}
\n ![\"issue](\"https://img.shields.io/badge/Oz%20agents-triaging%20issues-white?logo=warp\"){kind=icon}
![\"discord](\"https://img.shields.io/badge/chat-discord-blue?style=flat&logo=discord\"){kind=icon}
\n\n# Vite ⚡\n\n> Next Generation Frontend Tooling\n\n- 💡 Instant Server Start\n- ⚡️ Lightning Fast HMR\n- 🛠️ Rich Features\n- 📦 Optimized Build\n- 🔩 Universal Plugin Interface\n- 🔑 Fully Typed APIs\n\nVite (French word for \"quick\", pronounced [`/viːt/`](https://cdn.jsdelivr.net/gh/vitejs/vite@main/docs/public/vite.mp3), like \"veet\") is a new breed of frontend build tooling that significantly improves the frontend development experience. It consists of two major parts:\n\n- A dev server that serves your source files over [native ES modules](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules), with [rich built-in features](https://vite.dev/guide/features.html) and astonishingly fast [Hot Module Replacement (HMR)](https://vite.dev/guide/features.html#hot-module-replacement).\n\n- A [build command](https://vite.dev/guide/build.html) that bundles your code with [Rollup](https://rollupjs.org), pre-configured to output highly optimized static assets for production.\n\nIn addition, Vite is highly extensible via its [Plugin API](https://vite.dev/guide/api-plugin.html) and [JavaScript API](https://vite.dev/guide/api-javascript.html) with full typing support.\n\n[Read the Docs to Learn More](https://vite.dev).\n\n## Packages\n\n| Package | Version (click for changelogs) |\n| ----------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------- |\n| [vite](packages/vite) | [](packages/vite/CHANGELOG.md) |\n| [@vitejs/plugin-legacy](packages/plugin-legacy) | [](packages/plugin-legacy/CHANGELOG.md) |\n| [create-vite](packages/create-vite) | [](packages/create-vite/CHANGELOG.md) |\n\n## Contribution\n\nSee [Contributing Guide](CONTRIBUTING.md).\n\n## License\n\n[MIT](LICENSE).\n\n## Sponsors\n\n
\n \n ![\"sponsors\"](\"https://sponsors.vuejs.org/vite.svg?v2\")
\n \n
Building Together
\nViteConf 2025
\nView the replays
\n \n \n- \n
- \n
\n \n \n \n
\n
\n\n\n\n"
},
{
"path": "docs/.vitepress/theme/components/SvgImage.vue",
"content": "\n\n\n - \n
- \n Regular patches are released for\n .\n \n
- \n Important fixes and security patches are backported to\n .\n \n
- \n Security patches are also backported to\n .\n \n
- \n All versions before these are no longer supported. Users should upgrade\n to receive updates.\n \n
\n If you're using Vite\n
\n \n
\n\n\n\n"
},
{
"path": "docs/.vitepress/theme/composables/sponsor.ts",
"content": "import { onMounted, onUnmounted, ref } from 'vue'\nimport type {\n Sponsor,\n SponsorTier,\n} from '@voidzero-dev/vitepress-theme/src/types/sponsors'\nimport voidZeroSvg from './images/voidzero.svg'\nimport boltSvg from './images/bolt.svg'\nimport nuxtLabsSvg from './images/nuxtlabs.svg'\n\ninterface Sponsors {\n special: Sponsor[]\n platinum: Sponsor[]\n platinum_china: Sponsor[]\n gold: Sponsor[]\n silver: Sponsor[]\n bronze: Sponsor[]\n}\n\n// shared data across instances so we load only once.\nconst data = ref\n \n \n \n
\n \n \n
\n Loved by the community
\n\n Don't take our word for it - listen to what Vite community members\n have to say.\n
\n\n
\n\n \n 75k+
\n\n
\n
\n 40m+
\nWeekly NPM downloads
\n\n \n \n \n
\n \n \n \n \n\n \n {{ paragraph }}\n \n
\n\n \n \n \n
\n \n {{\n testimonial.name\n }}\n {{\n testimonial.handle\n }}\n
\n \n
\n\n \n
\n \n Instant Server Start\n
\n\n On demand source file serving over native ESM, with blazing fast\n dependency pre-bundling.\n
\n\n
\n \n
\n\n \n
\n Lightning Fast HMR
\n\n Instantly reflect changes as you save, no matter how big your app is.\n
\n\n
\n \n
\n\n Rich Features Out of the Box
\n\n TypeScript, JSX, CSS, Workers, WebAssembly... and more just a plugin\n away.\n
\n\n
\n \n\n
\n Optimized Build
\n\n Advanced tree-shaking, built-in minification, fine-grained chunking\n control powered by Rolldown.\n
\n\n
\n \n
\n\n \n Flexible Plugin System\n
\n\n Vite plugins extends Rollup's well-designed plugin interface with a few\n extra Vite-specific options.\n
\n\n
\n\n \n
\n Fully Typed API
\nDesigned to be built on top of.
\n\n
\n \n
\n\n First class SSR Support
\n\n It's never been easier to setup custom SSR (Server-Side Rendering), or\n build your own SSR framework.\n
\n\n
\n \n\n
\n Continuous ecosystem integration
\n\n Our CI continuously tests Vite changes against downstream projects,\n allowing us to improve Vite with stability and confidence.\n
\n\n
\n \n The Build Tool for the Web\n
\n\n Vite is a blazing fast frontend build tool powering the next\n generation of web applications.\n
\n\n \n Get Started\n \n \n View on GitHub\n \n
\n \n \n \n
\n \n \n\n \n Previous events\n \n
\n\n\n\n"
},
{
"path": "docs/.vitepress/theme/live/Hero.vue",
"content": "\n \n \n
\n \n
\n \n \n {{ event.title }}\n
\n\n 5th anniversary of the Vite Team Creation\n
\n\n Vite: The Documentary re-premiere\n
\n\n Join the ecosystem this March 19th at 3 PM UTC to remember the story we\n wrote together. And participate in the live stage to discuss our past,\n present, and future. We'll be waiting for you!\n
\n\n \n
\n \n \n \n Add to Calendar\n \n \n Join Community\n \n
\n \n
\n \n\n
\n \n\n \n Chat with us\n \n \n \n \n \n \n \n \n \n
\n \n
\n\n## Dependencies\n\nVite depends on these amazing open source projects:\n\n### Notable Dependencies\n\n\n
\n\n### Bundled Dependency Authors\n\n\n
\n\n
\n \n {{ dep.name }}\n \n Repo\n Sponsor\n \n {{ dep.description }}
\n| Author | \nPackages | \n
|---|---|
| \n {{ author.name }}\n {{ author.name }}\n Sponsor\n | \n\n \n {{ pkg.name }}Sponsor, \n \n | \n
\n
\n\n## Past Notable Dependencies\n\nWe also thank the maintainers of these projects that Vite used in previous versions:\n\n\n
\n\n
\n \n {{ dep.name }}\n \n Repo\n Sponsor\n \n {{ dep.description }}
\n| Package | \nDescription | \nLinks | \n
|---|---|---|
{{ dep.name }} | \n {{ dep.description }} | \nRepo | \n
\n ![](\"/logo.svg\"){kind=logo}
\n
\n![\"Vite](\"../images/vite.svg\")
\n![\"Vue](\"../images/vue.svg\")
\n![\"Svelte](\"../images/svelte.svg\")
\n![\"React](\"../images/react.svg\")
\n![\"Preact](\"../images/preact.svg\")
\n![\"Lit](\"../images/lit.svg\")
\n
\n\n\n\nThe theme is now shared by all templates. This should help better convey the scope for these starters as minimal templates to get started with Vite. For more complete solutions including linting, testing setup, and other features, there are official Vite-powered templates for some frameworks like [create-vue](https://github.com/vuejs/create-vue) and [create-svelte](https://github.com/sveltejs/kit). There is a community-maintained list of templates at [Awesome Vite](https://github.com/vitejs/awesome-vite#templates).\n\n## Dev Improvements\n\n### Vite CLI\n\n\n\n\n\n\n\n\n VITE v3.0.0 ready in 320 ms\n\n ➜ Local: http://127.0.0.1:5173/\n ➜ Network: use --host to expose\n\n\nApart from the CLI’s aesthetics improvements, you’ll notice that the default dev server port is now 5173 and the preview server listening at 4173. This change ensures Vite will avoid collisions with other tools.\n\n### Improved WebSocket Connection Strategy\n\nOne of the pain points of Vite 2 was configuring the server when running behind a proxy. Vite 3 changes the default connection scheme so it works out of the box in most scenarios. All these setups are now tested as part of the Vite Ecosystem CI through [`vite-setup-catalogue`](https://github.com/sapphi-red/vite-setup-catalogue).\n\n### Cold Start Improvements\n\nVite now avoids full reload during cold start when imports are injected by plugins while crawling the initial statically imported modules ([#8869](https://github.com/vitejs/vite/issues/8869)).\n\n
\n
\n\nClick to learn more
\n\nIn Vite 2.9, both the scanner and optimizer were run in the background. In the best scenario, where the scanner would find every dependency, no reload was needed in cold start. But if the scanner missed a dependency, a new optimization phase and then a reload were needed. Vite was able to avoid some of these reloads in v2.9, as we detected if the new optimized chunks were compatible with the ones the browser had. But if there was a common dep, the sub-chunks could change and a reload was required to avoid duplicated state. In Vite 3, the optimized deps aren't handed to the browser until the crawling of static imports is done. A quick optimization phase is issued if there is a missing dep (for example, injected by a plugin), and only then, the bundled deps are sent. So, a page reload is no longer needed for these cases.\n\n![\"Two](\"../images/vite-3-cold-start.svg\")
\n\n### import.meta.glob\n\n`import.meta.glob` support was rewritten. Read about the new features in the [Glob Import Guide](/guide/features.html#glob-import):\n\n[Multiple Patterns](/guide/features.html#multiple-patterns) can be passed as an array\n\n```js\nimport.meta.glob(['./dir/*.js', './another/*.js'])\n```\n\n[Negative Patterns](/guide/features.html#negative-patterns) are now supported (prefixed with `!`) to ignore some specific files\n\n```js\nimport.meta.glob(['./dir/*.js', '!**/bar.js'])\n```\n\n[Named Imports](/guide/features.html#named-imports) can be specified to improve tree-shaking\n\n```js\nimport.meta.glob('./dir/*.js', { import: 'setup' })\n```\n\n[Custom Queries](/guide/features.html#custom-queries) can be passed to attach metadata\n\n```js\nimport.meta.glob('./dir/*.js', { query: { custom: 'data' } })\n```\n\n[Eager Imports](/guide/features.html#glob-import) is now passed as a flag\n\n```js\nimport.meta.glob('./dir/*.js', { eager: true })\n```\n\n### Aligning WASM Import with Future Standards\n\nThe WebAssembly import API has been revised to avoid collisions with future standards and to make it more flexible:\n\n```js\nimport init from './example.wasm?init'\n\ninit().then((instance) => {\n instance.exports.test()\n})\n```\n\nLearn more in the [WebAssembly guide](/guide/features.html#webassembly)\n\n## Build Improvements\n\n### ESM SSR Build by Default\n\nMost SSR frameworks in the ecosystem were already using ESM builds. So, Vite 3 makes ESM the default format for SSR builds. This allows us to streamline previous [SSR externalization heuristics](https://vite.dev/guide/ssr.html#ssr-externals), externalizing dependencies by default.\n\n### Improved Relative Base Support\n\nVite 3 now properly supports relative base (using `base: ''`), allowing built assets to be deployed to different bases without re-building. This is useful when the base isn't known at build time, for example when deploying to content-addressable networks like [IPFS](https://ipfs.io/).\n\n## Experimental Features\n\n### Built Asset Paths fine-grained Control (Experimental)\n\nThere are other deploy scenarios where this isn't enough. For example, if the generated hashed assets need to be deployed to a different CDN from the public files, then finer-grained control is required over path generation at build time. Vite 3 provides an experimental API to modify the built file paths. Check [Build Advanced Base Options](/guide/build.html#advanced-base-options) for more information.\n\n### Esbuild Deps Optimization at Build Time (Experimental)\n\nOne of the main differences between dev and build time is how Vite handles dependencies. During build time, [`@rollup/plugin-commonjs`](https://github.com/rollup/plugins/tree/master/packages/commonjs) is used to allow importing CJS only dependencies (like React). When using the dev server, esbuild is used instead to pre-bundle and optimize dependencies, and an inline interop scheme is applied while transforming user code importing CJS deps. During the development of Vite 3, we introduced the changes needed to also allow the use of [esbuild to optimize dependencies during build time](https://v3.vite.dev/guide/migration.html#using-esbuild-deps-optimization-at-build-time). [`@rollup/plugin-commonjs`](https://github.com/rollup/plugins/tree/master/packages/commonjs) can then be avoided, making dev and build time work in the same way.\n\nGiven that Rollup v3 will be out in the next months, and we're going to follow up with another Vite major, we've decided to make this mode optional to reduce v3 scope and give Vite and the ecosystem more time to work out possible issues with the new CJS interop approach during build time. Frameworks may switch to using esbuild deps optimization during build time by default at their own pace before Vite 4.\n\n### HMR Partial Accept (Experimental)\n\nThere is opt-in support for [HMR Partial Accept](https://github.com/vitejs/vite/pull/7324). This feature could unlock finer-grained HMR for framework components that export several bindings in the same module. You can learn more at [the discussion for this proposal](https://github.com/vitejs/vite/discussions/7309).\n\n## Bundle Size Reduction\n\nVite cares about its publish and install footprint; a fast installation of a new app is a feature. Vite bundles most of its dependencies and tries to use modern lightweight alternatives where possible. Continuing with this ongoing goal, Vite 3 publish size is 30% smaller than v2.\n\n| | Publish Size | Install Size |\n| ----------- | :----------: | :----------: |\n| Vite 2.9.14 | 4.38MB | 19.1MB |\n| Vite 3.0.0 | 3.05MB | 17.8MB |\n| Reduction | -30% | -7% |\n\nIn part, this reduction was possible by making some dependencies that most users weren't needing optional. First, [Terser](https://github.com/terser/terser) is no longer installed by default. This dependency was no longer needed since we already made esbuild the default minifier for both JS and CSS in Vite 2. If you use `build.minify: 'terser'`, you'll need to install it (`npm add -D terser`). We also moved [node-forge](https://github.com/digitalbazaar/forge) out of the monorepo, implementing support for automatic https certificate generation as a new plugin: [`@vitejs/plugin-basic-ssl`](https://v3.vite.dev/guide/migration.html#automatic-https-certificate-generation). Since this feature only creates untrusted certificates that are not added to the local store, it didn't justify the added size.\n\n## Bug Fixing\n\nA triaging marathon was spearheaded by [@bluwyoo](https://twitter.com/bluwyoo), [@sapphi_red](https://twitter.com/sapphi_red), that recently joined the Vite team. During the past three months, the Vite open issues were reduced from 770 to 400. And this dive was achieved while the newly open PRs were at an all-time high. At the same time, [@haoqunjiang](https://twitter.com/haoqunjiang) had also curated a comprehensive [overview of Vite issues](https://github.com/vitejs/vite/discussions/8232).\n\n[](https://www.repotrends.com/vitejs/vite)\n\n[](https://www.repotrends.com/vitejs/vite)\n\n## Compatibility Notes\n\n- Vite no longer supports Node.js 12 / 13 / 15, which reached its EOL. Node.js 14.18+ / 16+ is now required.\n- Vite is now published as ESM, with a CJS proxy to the ESM entry for compatibility.\n- The Modern Browser Baseline now targets browsers which support the [native ES Modules](https://caniuse.com/es6-module), [native ESM dynamic import](https://caniuse.com/es6-module-dynamic-import), and [`import.meta`](https://caniuse.com/mdn-javascript_operators_import_meta) features.\n- JS file extensions in SSR and library mode now use a valid extension (`js`, `mjs`, or `cjs`) for output JS entries and chunks based on their format and the package type.\n\nLearn more in the [Migration Guide](https://v3.vite.dev/guide/migration.html).\n\n## Upgrades to Vite Core\n\nWhile working towards Vite 3, we also improved the contributing experience for collaborators to [Vite Core](https://github.com/vitejs/vite).\n\n- Unit and E2E tests have been migrated to [Vitest](https://vitest.dev), providing a faster and more stable DX. This move also works as dog fooding for an important infrastructure project in the ecosystem.\n- VitePress build is now tested as part of CI.\n- Vite upgraded to [pnpm 7](https://pnpm.io/), following the rest of the ecosystem.\n- Playgrounds have been moved to [`/playgrounds`](https://github.com/vitejs/vite/tree/main/playground) out of packages directory.\n- The packages and playgrounds are now `\"type\": \"module\"`.\n- Plugins are now bundled using [unbuild](https://github.com/unjs/unbuild), and [plugin-vue-jsx](https://github.com/vitejs/vite-plugin-vue/tree/main/packages/plugin-vue-jsx) and [plugin-legacy](https://github.com/vitejs/vite/tree/main/packages/plugin-legacy) were moved to TypeScript.\n\n## The Ecosystem is Ready for v3\n\nWe have worked closely with projects in the ecosystem to ensure that frameworks powered by Vite are ready for Vite 3. [vite-ecosystem-ci](https://github.com/vitejs/vite-ecosystem-ci) allows us to run the CI's from the leading players in the ecosystem against Vite's main branch and receive timely reports before introducing a regression. Today's release should soon be compatible with most projects using Vite.\n\n## Acknowledgments\n\nVite 3 is the result of the aggregate effort of members of the [Vite Team](/team) working together with ecosystem project maintainers and other collaborators to Vite core.\n\nWe want to thank everyone who has implemented features, and fixes, given feedback, and have been involved in Vite 3:\n\n- Vite team members [@youyuxi](https://twitter.com/youyuxi), [@patak_dev](https://twitter.com/patak_dev), [@antfu7](https://twitter.com/antfu7), [@bluwyoo](https://twitter.com/bluwyoo), [@sapphi_red](https://twitter.com/sapphi_red), [@haoqunjiang](https://twitter.com/haoqunjiang), [@poyoho](https://github.com/poyoho), [@Shini_92](https://twitter.com/Shini_92), and [@retropragma](https://twitter.com/retropragma).\n- [@benmccann](https://github.com/benmccann), [@danielcroe](https://twitter.com/danielcroe), [@brillout](https://twitter.com/brillout), [@sheremet_va](https://twitter.com/sheremet_va), [@userquin](https://twitter.com/userquin), [@enzoinnocenzi](https://twitter.com/enzoinnocenzi), [@maximomussini](https://twitter.com/maximomussini), [@IanVanSchooten](https://twitter.com/IanVanSchooten), the [Astro team](https://astro.build/), and all other maintainers of frameworks and plugins in the ecosystem in that helped shape v3.\n- [@dominikg](https://github.com/dominikg) for his work on vite-ecosystem-ci.\n- [@ZoltanKochan](https://twitter.com/ZoltanKochan) for his work on [pnpm](https://pnpm.io/), and for his responsiveness when we needed support with it.\n- [@rixo](https://github.com/rixo) for HMR Partial Accept support.\n- [@KiaKing85](https://twitter.com/KiaKing85) for getting the theme ready for the Vite 3 release, and [@\\_brc_dd](https://twitter.com/_brc_dd) for working on the VitePress internals.\n- [@CodingWithCego](https://twitter.com/CodingWithCego) for the new Spanish translation, and [@ShenQingchuan](https://twitter.com/ShenQingchuan), [@hiro-lapis](https://github.com/hiro-lapis) and others in the Chinese and Japanese translations teams for keeping the translated docs up to date.\n\nWe also want to thank individuals and companies sponsoring the Vite team, and companies investing in Vite development: some of [@antfu7](https://twitter.com/antfu7)'s work on Vite and the ecosystem is part of his job at [Nuxt Labs](https://nuxtlabs.com/), and [StackBlitz](https://stackblitz.com/) hired [@patak_dev](https://twitter.com/patak_dev) to work full time on Vite.\n\n## What's Next\n\nWe'll take the following months to ensure a smooth transition for all the projects built on top of Vite. So the first minors will be focused on continuing our triaging efforts with a focus on newly opened issues.\n\nThe Rollup team is [working on its next major](https://twitter.com/lukastaegert/status/1544186847399743488), to be released in the following months. Once the Rollup plugins ecosystem has time to update, we'll follow up with a new Vite major. This will give us another opportunity to introduce more significant changes this year, which we could take to stabilize some of the experimental features introduced in this release.\n\nIf you are interested in helping improve Vite, the best way to get on board is to help with triaging issues. Join [our Discord](https://chat.vite.dev) and look for the `#contributing` channel. Or get involved in our `#docs`, `#help` others, or create plugins. We are just getting started. There are many open ideas to keep improving Vite's DX.\n"
},
{
"path": "docs/blog/announcing-vite4-3.md",
"content": "---\ntitle: Vite 4.3 is out!\nauthor:\n name: The Vite Team\ndate: 2023-04-20\nsidebar: false\nhead:\n - - meta\n - property: og:type\n content: website\n - - meta\n - property: og:title\n content: Announcing Vite 4.3\n - - meta\n - property: og:image\n content: https://vite.dev/og-image-announcing-vite4-3.webp\n - - meta\n - property: og:url\n content: https://vite.dev/blog/announcing-vite4-3\n - - meta\n - property: og:description\n content: Vite 4.3 Release Announcement\n - - meta\n - name: twitter:card\n content: summary_large_image\n---\n\n# Vite 4.3 is out!\n\n_April 20, 2023_\n\n\n\nQuick links:\n\n- Docs: [English](/), [简体中文](https://cn.vite.dev/), [日本語](https://ja.vite.dev/), [Español](https://es.vite.dev/), [Português](https://pt.vite.dev/)\n- [Vite 4.3 Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md#430-2023-04-20)\n\n## Performance Improvements\n\nIn this minor, we focused on improving the dev server performance. The resolve logic got streamlined, improving hot paths and implementing smarter caching for finding `package.json`, TS config files, and resolved URL in general.\n\nYou can read a detailed walkthrough of the performance work done in this blog post by one of Vite Contributors: [How we made Vite 4.3 faaaaster 🚀](https://sun0day.github.io/blog/vite/why-vite4_3-is-faster.html).\n\nThis sprint resulted in speed improvements across the board compared to Vite 4.2.\n\nThese are the performance improvements as measured by [sapphi-red/performance-compare](https://github.com/sapphi-red/performance-compare), which tests an app with 1000 React Components cold and warm dev server startup time as well as HMR times for a root and a leaf component:\n\n| **Vite (babel)** | Vite 4.2 | Vite 4.3 | Improvement |\n| :----------------- | --------: | -------: | ----------: |\n| **dev cold start** | 17249.0ms | 5132.4ms | -70.2% |\n| **dev warm start** | 6027.8ms | 4536.1ms | -24.7% |\n| **Root HMR** | 46.8ms | 26.7ms | -42.9% |\n| **Leaf HMR** | 27.0ms | 12.9ms | -52.2% |\n\n| **Vite (swc)** | Vite 4.2 | Vite 4.3 | Improvement |\n| :----------------- | --------: | -------: | ----------: |\n| **dev cold start** | 13552.5ms | 3201.0ms | -76.4% |\n| **dev warm start** | 4625.5ms | 2834.4ms | -38.7% |\n| **Root HMR** | 30.5ms | 24.0ms | -21.3% |\n| **Leaf HMR** | 16.9ms | 10.0ms | -40.8% |\n\n\n\n\n\nYou can read more information about the benchmark [here](https://gist.github.com/sapphi-red/25be97327ee64a3c1dce793444afdf6e). Specs and Versions for this performance run:\n\n- CPU: Ryzen 9 5900X, Memory: DDR4-3600 32GB, SSD: WD Blue SN550 NVME SSD\n- Windows 10 Pro 21H2 19044.2846\n- Node.js 18.16.0\n- Vite and React Plugin versions\n - Vite 4.2 (babel): Vite 4.2.1 + plugin-react 3.1.0\n - Vite 4.3 (babel): Vite 4.3.0 + plugin-react 4.0.0-beta.1\n - Vite 4.2 (swc): Vite 4.2.1 + plugin-react-swc 3.2.0\n - Vite 4.3 (swc): Vite 4.3.0 + plugin-react-swc 3.3.0\n\nEarly adopters have also reported seeing 1.5x-2x dev startup time improvement on real apps while testing the Vite 4.3 beta. We'd love to know the results for your apps.\n\n## Profiling\n\nWe'll continue to work on Vite's performance. We're working on an official [Benchmark tool](https://github.com/vitejs/vite-benchmark) for Vite that let us get performance metrics for each Pull Request.\n\nAnd [vite-plugin-inspect](https://github.com/antfu/vite-plugin-inspect) now has more performance-related features to help you identify which plugins or middlewares are the bottleneck for your applications.\n\nUsing `vite --profile` (and then pressing `p`) once the page loads will save a CPU profile of the dev server startup. You can open them in an app as [speedscope](https://www.speedscope.app/) to identify performance issues. And you can share your findings with the Vite Team in a [Discussion](https://github.com/vitejs/vite/discussions) or in [Vite's Discord](https://chat.vite.dev).\n\n## Next Steps\n\nWe decided to do a single Vite Major this year aligning with the [EOL of Node.js 16](https://endoflife.date/nodejs) in September, dropping support for both Node.js 14 and 16 in it. If you would like to get involved, we started a [Vite 5 Discussion](https://github.com/vitejs/vite/discussions/12466) to gather early feedback.\n"
},
{
"path": "docs/blog/announcing-vite4.md",
"content": "---\ntitle: Vite 4.0 is out!\nauthor:\n name: The Vite Team\ndate: 2022-12-09\nsidebar: false\nhead:\n - - meta\n - property: og:type\n content: website\n - - meta\n - property: og:title\n content: Announcing Vite 4\n - - meta\n - property: og:image\n content: https://vite.dev/og-image-announcing-vite4.webp\n - - meta\n - property: og:url\n content: https://vite.dev/blog/announcing-vite4\n - - meta\n - property: og:description\n content: Vite 4 Release Announcement\n - - meta\n - name: twitter:card\n content: summary_large_image\n---\n\n# Vite 4.0 is out!\n\n_December 9, 2022_ - Check out the [Vite 5.0 announcement](./announcing-vite5.md)\n\nVite 3 [was released](./announcing-vite3.md) five months ago. npm downloads per week have gone from 1 million to 2.5 million since then. The ecosystem has matured too, and continues to grow. In this year's [Jamstack Conf survey](https://twitter.com/vite_js/status/1589665610119585793), usage among the community jumped from 14% to 32% while keeping a high 9.7 satisfaction score. We saw the stable releases of [Astro 1.0](https://astro.build/), [Nuxt 3](https://v3.nuxtjs.org/), and other Vite-powered frameworks that are innovating and collaborating: [SvelteKit](https://kit.svelte.dev/), [Solid Start](https://www.solidjs.com/blog/introducing-solidstart), [Qwik City](https://qwik.builder.io/qwikcity/overview/). Storybook announced first-class support for Vite as one of its main features for [Storybook 7.0](https://storybook.js.org/blog/first-class-vite-support-in-storybook/). Deno now [supports Vite](https://www.youtube.com/watch?v=Zjojo9wdvmY). [Vitest](https://vitest.dev) adoption is exploding, it will soon represent half of Vite's npm downloads. Nx is also investing in the ecosystem, and [officially supports Vite](https://nx.dev/packages/vite).\n\n[](https://viteconf.org/2022/replay)\n\nAs a showcase of the growth Vite and related projects have experienced, the Vite ecosystem gathered on October 11th at [ViteConf 2022](https://viteconf.org/2022/replay). We saw representatives from the main web framework and tools tell stories of innovation and collaboration. And in a symbolic move, the Rollup team choose that exact day to release [Rollup 3](https://rollupjs.org).\n\nToday, the Vite [team](https://vite.dev/team) with the help of our ecosystem partners, is happy to announce the release of Vite 4, powered during build time by Rollup 3. We've worked with the ecosystem to ensure a smooth upgrade path for this new major. Vite is now using [Rollup 3](https://github.com/vitejs/vite/issues/9870), which allowed us to simplify Vite's internal asset handling and has many improvements. See the [Rollup 3 release notes here](https://github.com/rollup/rollup/releases/tag/v3.0.0).\n\n\n\nQuick links:\n\n- [Docs](/)\n- [Migration Guide](https://v4.vite.dev/guide/migration.html)\n- [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md#400-2022-12-09)\n\nDocs in other languages:\n\n- [简体中文](https://cn.vite.dev/)\n- [日本語](https://ja.vite.dev/)\n- [Español](https://es.vite.dev/)\n\nIf you recently started using Vite, we suggest reading the [Why Vite Guide](https://vite.dev/guide/why.html) and checking out [the Getting Started](https://vite.dev/guide/) and [Features guide](https://vite.dev/guide/features). If you want to get involved, contributions are welcome at [GitHub](https://github.com/vitejs/vite). Almost [700 collaborators](https://github.com/vitejs/vite/graphs/contributors) have contributed to Vite. Follow the updates on [Twitter](https://twitter.com/vite_js) and [Mastodon](https://webtoo.ls/@vite), or collaborate with others on our [Discord community](https://chat.vite.dev).\n\n## Start playing with Vite 4\n\nUse `pnpm create vite` to scaffold a Vite project with your preferred framework, or open a started template online to play with Vite 4 using [vite.new](https://vite.new).\n\nYou can also run `pnpm create vite-extra` to get access to templates from other frameworks and runtimes (Solid, Deno, SSR, and library starters). `create vite-extra` templates are also available when you run `create vite` under the `Others` option.\n\nNote that Vite starter templates are intended to be used as a playground to test Vite with different frameworks. When building your next project, we recommend reaching out to the starters recommended by each framework. Some frameworks now redirect in `create vite` to their starters too (`create-vue` and `Nuxt 3` for Vue, and `SvelteKit` for Svelte).\n\n## New React plugin using SWC during development\n\n[SWC](https://swc.rs/) is now a mature replacement for [Babel](https://babeljs.io/), especially in the context of React projects. SWC's React Fast Refresh implementation is a lot faster than Babel, and for some projects, it is now a better alternative. From Vite 4, two plugins are available for React projects with different tradeoffs. We believe that both approaches are worth supporting at this point, and we'll continue to explore improvements to both plugins in the future.\n\n### @vitejs/plugin-react\n\n[@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react) is a plugin that uses esbuild and Babel, achieving fast HMR with a small package footprint and the flexibility of being able to use the Babel transform pipeline.\n\n### @vitejs/plugin-react-swc (new)\n\n[@vitejs/plugin-react-swc](https://github.com/vitejs/vite-plugin-react-swc) is a new plugin that uses esbuild during build, but replaces Babel with SWC during development. For big projects that don't require non-standard React extensions, cold start and Hot Module Replacement (HMR) can be significantly faster.\n\n## Browser Compatibility\n\nThe modern browser build now targets `safari14` by default for wider ES2020 compatibility. This means that modern builds can now use [`BigInt`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt) and that the [nullish coalescing operator](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Nullish_coalescing) isn't transpiled anymore. If you need to support older browsers, you can add [`@vitejs/plugin-legacy`](https://github.com/vitejs/vite/tree/main/packages/plugin-legacy) as usual.\n\n## Importing CSS as a String\n\nIn Vite 3, importing the default export of a `.css` file could introduce a double loading of CSS.\n\n```ts\nimport cssString from './global.css'\n```\n\nThis double loading could occur since a `.css` file will be emitted and it's likely that the CSS string will also be used by the application code — for example, injected by the framework runtime. From Vite 4, the `.css` default export [has been deprecated](https://github.com/vitejs/vite/issues/11094). The `?inline` query suffix modifier needs to be used in this case, as that doesn't emit the imported `.css` styles.\n\n```ts\nimport stuff from './global.css?inline'\n```\n\nLearn more in the [Migration Guide](https://v4.vite.dev/guide/migration.html).\n\n## Environment Variables\n\nVite now uses `dotenv` 16 and `dotenv-expand` 9 (previously `dotenv` 14 and `dotenv-expand` 5). If you have a value including `#` or `` ` ``, you will need to wrap them with quotes.\n\n```diff\n-VITE_APP=ab#cd`ef\n+VITE_APP=\"ab#cd`ef\"\n```\n\nFor more details, see the [`dotenv`](https://github.com/motdotla/dotenv/blob/master/CHANGELOG.md) and [`dotenv-expand` changelog](https://github.com/motdotla/dotenv-expand/blob/master/CHANGELOG.md).\n\n## Other Features\n\n- CLI Shortcuts (press `h` during dev to see them all) ([#11228](https://github.com/vitejs/vite/pull/11228))\n- Support for patch-package when pre bundling dependencies ([#10286](https://github.com/vitejs/vite/issues/10286))\n- Cleaner build logs output ([#10895](https://github.com/vitejs/vite/issues/10895)) and switch to `kB` to align with browser dev tools ([#10982](https://github.com/vitejs/vite/issues/10982))\n- Improved error messages during SSR ([#11156](https://github.com/vitejs/vite/issues/11156))\n\n## Reduced Package Size\n\nVite cares about its footprint, to speed up installation, especially in the use case of playgrounds for documentation and reproductions. And once more, this major brings improvements in Vite's package size. Vite 4 install size is 23% smaller compared to vite 3.2.5 (14.1 MB vs 18.3 MB).\n\n## Upgrades to Vite Core\n\n[Vite Core](https://github.com/vitejs/vite) and [vite-ecosystem-ci](https://github.com/vitejs/vite-ecosystem-ci) continue to evolve to provide a better experience to maintainers and collaborators and to ensure that Vite development scales to cope with the growth in the ecosystem.\n\n### Framework plugins out of core\n\n[`@vitejs/plugin-vue`](https://github.com/vitejs/vite-plugin-vue) and [`@vitejs/plugin-react`](https://github.com/vitejs/vite-plugin-react) have been part of Vite core monorepo since the first versions of Vite. This helped us to get a close feedback loop when making changes as we were getting both Core and the plugins tested and released together. With [vite-ecosystem-ci](https://github.com/vitejs/vite-ecosystem-ci) we can get this feedback with these plugins developed on independent repositories, so from Vite 4, [they have been moved out of the Vite core monorepo](https://github.com/vitejs/vite/pull/11158). This is meaningful for Vite's framework-agnostic story and will allow us to build independent teams to maintain each of the plugins. If you have bugs to report or features to request, please create issues on the new repositories moving forward: [`vitejs/vite-plugin-vue`](https://github.com/vitejs/vite-plugin-vue) and [`vitejs/vite-plugin-react`](https://github.com/vitejs/vite-plugin-react).\n\n### vite-ecosystem-ci improvements\n\n[vite-ecosystem-ci](https://github.com/vitejs/vite-ecosystem-ci) extends Vite's CI by providing on-demand status reports on the state of the CIs of [most major downstream projects](https://github.com/vitejs/vite-ecosystem-ci/tree/main/tests). We run vite-ecosystem-ci three times a week against Vite's main branch and receive timely reports before introducing a regression. Vite 4 will soon be compatible with most projects using Vite, which already prepared branches with the needed changes and will be releasing them in the next few days. We are also able to run vite-ecosystem-ci on-demand on PRs using `/ecosystem-ci run` in a comment, allowing us to know [the effect of changes](https://github.com/vitejs/vite/pull/11269#issuecomment-1343365064) before they hit main.\n\n## Acknowledgments\n\nVite 4 wouldn't be possible without uncountable hours of work by Vite contributors, many of them maintainers of downstream projects and plugins, and the efforts of the [Vite Team](/team). All of us have worked together to improve Vite's DX once more, for every framework and app using it. We're grateful to be able to improve a common base for such a vibrant ecosystem.\n\nWe're also thankful to individuals and companies sponsoring the Vite team, and companies investing directly in Vite's future: [@antfu7](https://twitter.com/antfu7)'s work on Vite and the ecosystem is part of his job at [Nuxt Labs](https://nuxtlabs.com/), [Astro](https://astro.build) is funding [@bluwyoo](https://twitter.com/bluwyoo)'s Vite core work, and [StackBlitz](https://stackblitz.com/) hires [@patak_dev](https://twitter.com/patak_dev) to work full time on Vite.\n\n## Next steps\n\nOur immediate focus would be on triaging newly opened issues to avoid disruption by possible regressions. If you would like to get involved and help us improve Vite, we suggest starting with issues triaging. Join [our Discord](https://chat.vite.dev) and reach out on the `#contributing` channel. Polish our `#docs` story, and `#help` others. We need to continue to build a helpful and welcoming community for the next wave of users, as Vite's adoption continues to grow.\n\nThere are a lot of open fronts to keep improving the DX of everyone that has chosen Vite to power their frameworks and develop their apps. Onwards!\n"
},
{
"path": "docs/blog/announcing-vite5-1.md",
"content": "---\ntitle: Vite 5.1 is out!\nauthor:\n name: The Vite Team\ndate: 2024-02-08\nsidebar: false\nhead:\n - - meta\n - property: og:type\n content: website\n - - meta\n - property: og:title\n content: Announcing Vite 5.1\n - - meta\n - property: og:image\n content: https://vite.dev/og-image-announcing-vite5-1.webp\n - - meta\n - property: og:url\n content: https://vite.dev/blog/announcing-vite5-1\n - - meta\n - property: og:description\n content: Vite 5.1 Release Announcement\n - - meta\n - name: twitter:card\n content: summary_large_image\n---\n\n# Vite 5.1 is out!\n\n_February 8, 2024_\n\n\n\nVite 5 [was released](./announcing-vite5.md) last November, and it represented another big leap for Vite and the ecosystem. A few weeks ago we celebrated 10 million weekly npm downloads and 900 contributors to the Vite repo. Today, we're excited to announce the release of Vite 5.1.\n\nQuick links: [Docs](/), [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md#510-2024-02-08)\n\nDocs in other languages: [简体中文](https://cn.vite.dev/), [日本語](https://ja.vite.dev/), [Español](https://es.vite.dev/), [Português](https://pt.vite.dev/), [한국어](https://ko.vite.dev/), [Deutsch](https://de.vite.dev/)\n\nTry Vite 5.1 online in StackBlitz: [vanilla](https://vite.new/vanilla-ts), [vue](https://vite.new/vue-ts), [react](https://vite.new/react-ts), [preact](https://vite.new/preact-ts), [lit](https://vite.new/lit-ts), [svelte](https://vite.new/svelte-ts), [solid](https://vite.new/solid-ts), [qwik](https://vite.new/qwik-ts).\n\nIf you're new to Vite, we suggest reading first the [Getting Started](/guide/) and [Features](/guide/features) guides.\n\nTo stay up to date, follow us on [X](https://x.com/vite_js) or [Mastodon](https://webtoo.ls/@vite).\n\n## Vite Runtime API\n\nVite 5.1 adds experimental support for a new Vite Runtime API. It allows running any code by processing it with Vite plugins first. It is different from `server.ssrLoadModule` because the runtime implementation is decoupled from the server. This lets library and framework authors implement their own layer of communication between the server and the runtime. This new API is intended to replace Vite's current SSR primitives once it is stable.\n\nThe new API brings many benefits:\n\n- Support for HMR during SSR.\n- It is decoupled from the server, so there is no limit on how many clients can use a single server - every client has its own module cache (you can even communicate with it how you want - using message channel/fetch call/direct function call/websocket).\n- It doesn't depend on any node/bun/deno built-in APIs, so it can run in any environment.\n- It's easy to integrate with tools that have their own mechanism to run code (you can provide a runner to use `eval` instead of `new AsyncFunction` for example).\n\nThe initial idea [was proposed by Pooya Parsa](https://github.com/nuxt/vite/pull/201) and implemented by [Anthony Fu](https://github.com/antfu) as the [vite-node](https://github.com/vitest-dev/vitest/tree/main/packages/vite-node#readme) package to [power Nuxt 3 Dev SSR](https://antfu.me/posts/dev-ssr-on-nuxt) and later also used as the base for [Vitest](https://vitest.dev). So the general idea of vite-node has been battle-tested for quite some time now. This is a new iteration of the API by [Vladimir Sheremet](https://github.com/sheremet-va), who had already re-implemented vite-node in Vitest and took the learnings to make the API even more powerful and flexible when adding it to Vite Core. The PR was one year in the makings, you can see the evolution and discussions with ecosystem maintainers [here](https://github.com/vitejs/vite/issues/12165).\n\n::: info\nThe Vite Runtime API evolved into the Module Runner API, released in Vite 6 as part of the [Environment API](/guide/api-environment).\n:::\n\n## Features\n\n### Improved support for `.css?url`\n\nImport CSS files as URLs now works reliably and correctly. This was the last remaining hurdle in Remix's move to Vite. See ([#15259](https://github.com/vitejs/vite/issues/15259)).\n\n### `build.assetsInlineLimit` now supports a callback\n\nUsers can now [provide a callback](/config/build-options.html#build-assetsinlinelimit) that returns a boolean to opt-in or opt-out of inlining for specific assets. If `undefined` is returned, the default logic applies. See ([#15366](https://github.com/vitejs/vite/issues/15366)).\n\n### Improved HMR for circular import\n\nIn Vite 5.0, accepted modules within circular imports always triggered a full page reload even if they can be handled fine in the client. This is now relaxed to allow HMR to apply without a full page reload, but if any error happens during HMR, the page will be reloaded. See ([#15118](https://github.com/vitejs/vite/issues/15118)).\n\n### Support `ssr.external: true` to externalize all SSR packages\n\nHistorically, Vite externalizes all packages except for linked packages. This new option can be used to force externalize all packages including linked packages too. This is handy in tests within monorepos where we want to emulate the usual case of all packages externalized, or when using `ssrLoadModule` to load an arbitrary file and we want to always external packages as we don't care about HMR. See ([#10939](https://github.com/vitejs/vite/issues/10939)).\n\n### Expose `close` method in the preview server\n\nThe preview server now exposes a `close` method, which will properly teardown the server including all opened socket connections. See ([#15630](https://github.com/vitejs/vite/issues/15630)).\n\n## Performance improvements\n\nVite keeps getting faster with each release, and Vite 5.1 is packed with performance improvements. We measured the loading time for 10K modules (25 level deep tree) using [vite-dev-server-perf](https://github.com/yyx990803/vite-dev-server-perf) for all minor versions from Vite 4.0. This is a good benchmark to measure the effect of Vite's bundle-less approach. Each module is a small TypeScript file with a counter and imports to other files in the tree, so this mostly measuring the time it takes to do the requests a separate modules. In Vite 4.0, loading 10K modules took 8 seconds on a M1 MAX. We had a breakthrough in [Vite 4.3 were we focused on performance](./announcing-vite4-3.md), and we were able to load them in 6.35 seconds. In Vite 5.1, we managed to do another performance leap. Vite is now serving the 10K modules in 5.35 seconds.\n\n\n\nThe results of this benchmark run on Headless Puppeteer and are a good way to compare versions. They don't represent the time as experienced by users though. When running the same 10K modules in an Incognito window is Chrome, we have:\n\n| 10K Modules | Vite 5.0 | Vite 5.1 |\n| --------------------- | :------: | :------: |\n| Loading time | 2892ms | 2765ms |\n| Loading time (cached) | 2778ms | 2477ms |\n| Full reload | 2003ms | 1878ms |\n| Full reload (cached) | 1682ms | 1604ms |\n\n### Run CSS preprocessors in threads\n\nVite now has opt-in support for running CSS preprocessors in threads. You can enable it using [`css.preprocessorMaxWorkers: true`](/config/shared-options.html#css-preprocessormaxworkers). For a Vuetify 2 project, dev startup time was reduced by 40% with this feature enabled. There is [performance comparison for others setups in the PR](https://github.com/vitejs/vite/pull/13584#issuecomment-1678827918). See ([#13584](https://github.com/vitejs/vite/issues/13584)). [Give Feedback](https://github.com/vitejs/vite/discussions/15835).\n\n### New options to improve server cold starts\n\nYou can set `optimizeDeps.holdUntilCrawlEnd: false` to switch to a new strategy for deps optimization that may help in big projects. We're considering switching to this strategy by default in the future. [Give Feedback](https://github.com/vitejs/vite/discussions/15834). ([#15244](https://github.com/vitejs/vite/issues/15244))\n\n### Faster resolving with cached checks\n\nThe `fs.cachedChecks` optimization is now enabled by default. In Windows, `tryFsResolve` was ~14x faster with it, and resolving ids overall got a ~5x speed up in the triangle benchmark. ([#15704](https://github.com/vitejs/vite/issues/15704))\n\n### Internal performance improvements\n\nThe dev server had several incremental performance gains. A new middleware to short-circuit on 304 ([#15586](https://github.com/vitejs/vite/issues/15586)). We avoided `parseRequest` in hot paths ([#15617](https://github.com/vitejs/vite/issues/15617)). Rollup is now properly lazy loaded ([#15621](https://github.com/vitejs/vite/issues/15621))\n\n## Deprecations\n\nWe continue to reduce Vite's API surface where possible to make the project maintainable long term.\n\n### Deprecated `as` option in `import.meta.glob`\n\nThe standard moved to [Import Attributes](https://github.com/tc39/proposal-import-attributes), but we don't plan to replace `as` with a new option at this point. Instead, it is recommended that the user switches to `query`. See ([#14420](https://github.com/vitejs/vite/issues/14420)).\n\n### Removed experimental build-time pre-bundling\n\nBuild-time pre-bundling, an experimental feature added in Vite 3, is removed. With Rollup 4 switching its parser to native, and Rolldown being worked on, both the performance and the dev-vs-build inconsistency story for this feature are no longer valid. We want to continue improving dev/build consistency, and have concluded that using Rolldown for \"prebundling during dev\" and \"production builds\" is the better bet moving forward. Rolldown may also implement caching in a way that is a lot more efficient during build than deps prebundling. See ([#15184](https://github.com/vitejs/vite/issues/15184)).\n\n## Get Involved\n\nWe are grateful to the [900 contributors to Vite Core](https://github.com/vitejs/vite/graphs/contributors), and the maintainers of plugins, integrations, tools, and translations that keeps pushing the ecosystem forward. If you're enjoying Vite, we invite you to participate and help us. Check out our [Contributing Guide](https://github.com/vitejs/vite/blob/main/CONTRIBUTING.md), and jump into [triaging issues](https://github.com/vitejs/vite/issues), [reviewing PRs](https://github.com/vitejs/vite/pulls), answering questions at [GitHub Discussions](https://github.com/vitejs/vite/discussions) and helping others in the community in [Vite Land](https://chat.vite.dev).\n\n## Acknowledgments\n\nVite 5.1 is possible thanks to our community of contributors, maintainers in the ecosystem, and the [Vite Team](/team). A shout out to the individuals and companies sponsoring Vite development. [StackBlitz](https://stackblitz.com/), [Nuxt Labs](https://nuxtlabs.com/), and [Astro](https://astro.build) for hiring Vite team members. And also to the sponsors on [Vite's GitHub Sponsors](https://github.com/sponsors/vitejs), [Vite's Open Collective](https://opencollective.com/vite), and [Evan You's GitHub Sponsors](https://github.com/sponsors/yyx990803).\n"
},
{
"path": "docs/blog/announcing-vite5.md",
"content": "---\ntitle: Vite 5.0 is out!\nauthor:\n name: The Vite Team\ndate: 2023-11-16\nsidebar: false\nhead:\n - - meta\n - property: og:type\n content: website\n - - meta\n - property: og:title\n content: Announcing Vite 5\n - - meta\n - property: og:image\n content: https://vite.dev/og-image-announcing-vite5.webp\n - - meta\n - property: og:url\n content: https://vite.dev/blog/announcing-vite5\n - - meta\n - property: og:description\n content: Vite 5 Release Announcement\n - - meta\n - name: twitter:card\n content: summary_large_image\n---\n\n# Vite 5.0 is out!\n\n_November 16, 2023_\n\n\n\nVite 4 [was released](./announcing-vite4.md) almost a year ago, and it served as a solid base for the ecosystem. npm downloads per week jumped from 2.5 million to 7.5 million, as projects keep building on a shared infrastructure. Frameworks continued to innovate, and on top of [Astro](https://astro.build/), [Nuxt](https://nuxt.com/), [SvelteKit](https://kit.svelte.dev/), [Solid Start](https://www.solidjs.com/blog/introducing-solidstart), [Qwik City](https://qwik.builder.io/qwikcity/overview/), between others, we saw new frameworks joining and making the ecosystem stronger. [RedwoodJS](https://redwoodjs.com/) and [Remix](https://remix.run/) switching to Vite paves the way for further adoption in the React ecosystem. [Vitest](https://vitest.dev) kept growing at an even faster pace than Vite. Its team has been hard at work and will soon [release Vitest 1.0](https://github.com/vitest-dev/vitest/issues/3596). The story of Vite when used with other tools such as [Storybook](https://storybook.js.org), [Nx](https://nx.dev), and [Playwright](https://playwright.dev) kept improving, and the same goes for environments, with Vite dev working both in [Deno](https://deno.com) and [Bun](https://bun.sh).\n\nWe had the second edition of [ViteConf](https://viteconf.org/23/replay) a month ago, hosted by [StackBlitz](https://stackblitz.com). Like last year, most of the projects in the ecosystem got together to share ideas and connect to keep expanding the commons. We're also seeing new pieces complement the meta-framework tool belt like [Volar](https://volarjs.dev/) and [Nitro](https://nitro.build/). The Rollup team released [Rollup 4](https://rollupjs.org) that same day, a tradition Lukas started last year.\n\nSix months ago, Vite 4.3 [was released](./announcing-vite4.md). This release significantly improved the dev server performance. However, there is still ample room for improvement. At ViteConf, [Evan You unveiled Vite's long-term plan to work on Rolldown](https://www.youtube.com/watch?v=hrdwQHoAp0M), a Rust-port of Rollup with compatible APIs. Once it is ready, we intend to use it in Vite Core to take on the tasks of both Rollup and esbuild. This will mean a boost in build performance (and later on in dev performance too as we move perf-sensitive parts of Vite itself to Rust), and a big reduction of inconsistencies between dev and build. Rolldown is currently in early stages and the team is preparing to open source the codebase before the end of the year. Stay tuned!\n\nToday, we mark another big milestone in Vite's path. The Vite [team](/team), [contributors](https://github.com/vitejs/vite/graphs/contributors), and ecosystem partners, are excited to announce the release of Vite 5. Vite is now using [Rollup 4](https://github.com/vitejs/vite/pull/14508), which already represents a big boost in build performance. And there are also new options to improve your dev server performance profile.\n\nVite 5 focuses on cleaning up the API (removing deprecated features) and streamlines several features closing long-standing issues, for example switching `define` to use proper AST replacements instead of regexes. We also continue to take steps to future-proof Vite (Node.js 18+ is now required, and [the CJS Node API has been deprecated](/guide/migration#deprecate-cjs-node-api)).\n\nQuick links:\n\n- [Docs](/)\n- [Migration Guide](/guide/migration)\n- [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md#500-2023-11-16)\n\nDocs in other languages:\n\n- [简体中文](https://cn.vite.dev/)\n- [日本語](https://ja.vite.dev/)\n- [Español](https://es.vite.dev/)\n- [Português](https://pt.vite.dev/)\n- [한국어](https://ko.vite.dev/)\n- [Deutsch](https://de.vite.dev/) (new translation!)\n\nIf you're new to Vite, we suggest reading first the [Getting Started](/guide/) and [Features](/guide/features) guides.\n\nWe appreciate the more than [850 contributors to Vite Core](https://github.com/vitejs/vite/graphs/contributors), and the maintainers and contributors of Vite plugins, integrations, tools, and translations that have helped us reach here. We encourage you to get involved and continue to improve Vite with us. You can learn more at our [Contributing Guide](https://github.com/vitejs/vite/blob/main/CONTRIBUTING.md). To get started, we recommend [triaging issues](https://github.com/vitejs/vite/issues), [reviewing PRs](https://github.com/vitejs/vite/pulls), sending failing tests PRs based on open issues, and helping others in [Discussions](https://github.com/vitejs/vite/discussions) and Vite Land's [help forum](https://discord.com/channels/804011606160703521/1019670660856942652). You'll learn a lot along the way and have a smooth path to further contributions to the project. If you have doubts, join us on our [Discord community](https://chat.vite.dev) and say hi on the [#contributing channel](https://discord.com/channels/804011606160703521/804439875226173480).\n\nTo stay up to date, follow us on [X](https://twitter.com/vite_js) or [Mastodon](https://webtoo.ls/@vite).\n\n## Quick start with Vite 5\n\nUse `pnpm create vite` to scaffold a Vite project with your preferred framework, or open a started template online to play with Vite 5 using [vite.new](https://vite.new). You can also run `pnpm create vite-extra` to get access to templates from other frameworks and runtimes (Solid, Deno, SSR, and library starters). `create vite-extra` templates are also available when you run `create vite` under the `Others` option.\n\nNote that Vite starter templates are intended to be used as a playground to test Vite with different frameworks. When building your next project, we recommend reaching out to the starters recommended by each framework. Some frameworks now redirect in `create vite` to their starters too (`create-vue` and `Nuxt 3` for Vue, and `SvelteKit` for Svelte).\n\n## Node.js Support\n\nVite no longer supports Node.js 14 / 16 / 17 / 19, which reached its EOL. Node.js 18 / 20+ is now required.\n\n## Performance\n\nOn top of Rollup 4's build performance improvements, there is a new guide to help you identify and fix common performance issues at [https://vite.dev/guide/performance](/guide/performance).\n\nVite 5 also introduces [server.warmup](/guide/performance.html#warm-up-frequently-used-files), a new feature to improve startup time. It lets you define a list of modules that should be pre-transformed as soon as the server starts. When using [`--open` or `server.open`](/config/server-options.html#server-open), Vite will also automatically warm up the entry point of your app or the provided URL to open.\n\n## Main Changes\n\n- [Vite is now powered by Rollup 4](/guide/migration#rollup-4)\n- [The CJS Node API has been deprecated](/guide/migration#deprecate-cjs-node-api)\n- [Rework `define` and `import.meta.env.*` replacement strategy](/guide/migration#rework-define-and-import-meta-env-replacement-strategy)\n- [SSR externalized modules value now matches production](/guide/migration#ssr-externalized-modules-value-now-matches-production)\n- [`worker.plugins` is now a function](/guide/migration#worker-plugins-is-now-a-function)\n- [Allow path containing `.` to fallback to index.html](/guide/migration#allow-path-containing-to-fallback-to-index-html)\n- [Align dev and preview HTML serving behavior](/guide/migration#align-dev-and-preview-html-serving-behaviour)\n- [Manifest files are now generated in `.vite` directory by default](/guide/migration#manifest-files-are-now-generated-in-vite-directory-by-default)\n- [CLI shortcuts require an additional `Enter` press](/guide/migration#cli-shortcuts-require-an-additional-enter-press)\n- [Update `experimentalDecorators` and `useDefineForClassFields` TypeScript behavior](/guide/migration#update-experimentaldecorators-and-usedefineforclassfields-typescript-behaviour)\n- [Remove `--https` flag and `https: true`](/guide/migration#remove-https-flag-and-https-true)\n- [Remove `resolvePackageEntry` and `resolvePackageData` APIs](/guide/migration#remove-resolvepackageentry-and-resolvepackagedata-apis)\n- [Removes previously deprecated APIs](/guide/migration#removed-deprecated-apis)\n- [Read more about advanced changes affecting plugin and tool authors](/guide/migration#advanced)\n\n## Migrating to Vite 5\n\nWe have worked with ecosystem partners to ensure a smooth migration to this new major. Once again, [vite-ecosystem-ci](https://www.youtube.com/watch?v=7L4I4lDzO48) has been crucial to help us make bolder changes while avoiding regressions. We're thrilled to see other ecosystems adopt similar schemes to improve the collaboration between their projects and downstream maintainers.\n\nFor most projects, the update to Vite 5 should be straight forward. But we advise reviewing the [detailed Migration Guide](/guide/migration) before upgrading.\n\nA low level breakdown with the full list of changes to Vite core can be found at the [Vite 5 Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md#500-2023-11-16).\n\n## Acknowledgments\n\nVite 5 is the result of long hours of work by our community of contributors, downstream maintainers, plugins authors, and the [Vite Team](/team). A big shout out to [Bjorn Lu](https://twitter.com/bluwyoo) for leading the release process for this major.\n\nWe're also thankful to individuals and companies sponsoring Vite development. [StackBlitz](https://stackblitz.com/), [Nuxt Labs](https://nuxtlabs.com/), and [Astro](https://astro.build) continue to invest in Vite by hiring Vite team members. A shout out to sponsors on [Vite's GitHub Sponsors](https://github.com/sponsors/vitejs), [Vite's Open Collective](https://opencollective.com/vite), and [Evan You's GitHub Sponsors](https://github.com/sponsors/yyx990803). A special mention to [Remix](https://remix.run/) for becoming a Gold sponsor and contributing back after switching to Vite.\n"
},
{
"path": "docs/blog/announcing-vite6.md",
"content": "---\ntitle: Vite 6.0 is out!\nauthor:\n name: The Vite Team\ndate: 2024-11-26\nsidebar: false\nhead:\n - - meta\n - property: og:type\n content: website\n - - meta\n - property: og:title\n content: Announcing Vite 6\n - - meta\n - property: og:image\n content: https://vite.dev/og-image-announcing-vite6.webp\n - - meta\n - property: og:url\n content: https://vite.dev/blog/announcing-vite6\n - - meta\n - property: og:description\n content: Vite 6 Release Announcement\n - - meta\n - name: twitter:card\n content: summary_large_image\n---\n\n# Vite 6.0 is out!\n\n_November 26, 2024_\n\n\n\nToday, we're taking another big step in Vite's story. The Vite [team](/team), [contributors](https://github.com/vitejs/vite/graphs/contributors), and ecosystem partners are excited to announce the release of Vite 6.\n\nIt has been an eventful year. Vite adoption keeps growing, with npm downloads per week jumping from 7.5 million to 17 million since the release of Vite 5 a year ago. [Vitest](https://vitest.dev) is not only being favored more by users but is also starting to form an ecosystem of its own. For example, [Storybook](https://storybook.js.org) has new testing capabilities powered by Vitest.\n\nNew frameworks have also joined the Vite ecosystem, including [TanStack Start](https://tanstack.com/start), [One](https://onestack.dev/), [Ember](https://emberjs.com/), and others. Web frameworks are innovating at an increasingly faster pace. You can check out the improvements folks have been doing at [Astro](https://astro.build/), [Nuxt](https://nuxt.com/), [SvelteKit](https://kit.svelte.dev/), [Solid Start](https://www.solidjs.com/blog/introducing-solidstart), [Qwik City](https://qwik.builder.io/qwikcity/overview/), [RedwoodJS](https://redwoodjs.com/), [React Router](https://reactrouter.com/), and the list goes on.\n\nVite is used by OpenAI, Google, Apple, Microsoft, NASA, Shopify, Cloudflare, GitLab, Reddit, Linear, among many others. Two months ago, we started a list of [companies using Vite](https://github.com/vitejs/companies-using-vite). We're happy to see many developers sending us a PR to add their companies to the list. It's hard to believe how much the ecosystem we built together has grown since Vite gave its first steps.\n\n\n\n## Speeding up the Vite ecosystem\n\nLast month, the community gathered for the third edition of [ViteConf](https://viteconf.org/24/replay), hosted once more by [StackBlitz](https://stackblitz.com). It was the biggest Vite conference, with a broad representation of builders from the ecosystem. Among other announcements, Evan You announced [VoidZero](https://staging.voidzero.dev/posts/announcing-voidzero-inc), a company dedicated to building an open-source, high-performance, and unified development toolchain for the JavaScript ecosystem. VoidZero is behind [Rolldown](https://rolldown.rs) and [Oxc](https://oxc.rs), and their team is making significant strides, getting them rapidly ready for being adopted by Vite. Watch Evan's keynote to learn more about the next steps for Vite's rust-powered future.\n\nOmit<RolldownOptions, 'input' | 'logLevel' | 'output'> & { output?: Omit<RolldownOutputOptions, 'format' | 'sourcemap' | 'dir' | 'banner'> }\n\nOptions to pass to Rolldown during the dep scanning and optimization.\n\nCertain options are omitted since changing them would not be compatible with Vite's dep optimization.\n\n- `plugins` are merged with Vite's dep plugin\n\n## optimizeDeps.esbuildOptions Omit<EsbuildBuildOptions, 'bundle' | 'entryPoints' | 'external' | 'write' | 'watch' | 'outdir' | 'outfile' | 'outbase' | 'outExtension' | 'metafile'>\n- **Deprecated**\n\nThis option is converted to `optimizeDeps.rolldownOptions` internally. Use `optimizeDeps.rolldownOptions` instead.\n\n## optimizeDeps.force \n
\n:::\n\n## `InlineConfig`\n\nThe `InlineConfig` interface extends `UserConfig` with additional properties:\n\n- `configFile`: specify config file to use. If not set, Vite will try to automatically resolve one from project root. Set to `false` to disable auto resolving.\n\n## `ResolvedConfig`\n\nThe `ResolvedConfig` interface has all the same properties of a `UserConfig`, except most properties are resolved and non-undefined. It also contains utilities like:\n\n- `config.assetsInclude`: A function to check if an `id` is considered an asset.\n- `config.logger`: Vite's internal logger object.\n\n## `ViteDevServer`\n\n```ts\ninterface ViteDevServer {\n /**\n * The resolved Vite config object.\n */\n config: ResolvedConfig\n /**\n * A connect app instance\n * - Can be used to attach custom middlewares to the dev server.\n * - Can also be used as the handler function of a custom http server\n * or as a middleware in any connect-style Node.js frameworks.\n *\n * https://github.com/senchalabs/connect#use-middleware\n */\n middlewares: Connect.Server\n /**\n * Native Node http server instance.\n * Will be null in middleware mode.\n */\n httpServer: http.Server | null\n /**\n * Chokidar watcher instance. If `config.server.watch` is set to `null`,\n * it will not watch any files and calling `add` or `unwatch` will have no effect.\n * https://github.com/paulmillr/chokidar/tree/3.6.0#api\n */\n watcher: FSWatcher\n /**\n * WebSocket server with `send(payload)` method.\n */\n ws: WebSocketServer\n /**\n * Rollup plugin container that can run plugin hooks on a given file.\n */\n pluginContainer: PluginContainer\n /**\n * Module graph that tracks the import relationships, url to file mapping\n * and hmr state.\n */\n moduleGraph: ModuleGraph\n /**\n * The resolved urls Vite prints on the CLI (URL-encoded). Returns `null`\n * in middleware mode or if the server is not listening on any port.\n */\n resolvedUrls: ResolvedServerUrls | null\n /**\n * Programmatically resolve, load and transform a URL and get the result\n * without going through the http request pipeline.\n */\n transformRequest(\n url: string,\n options?: TransformOptions,\n ): PromiseExample
\n\n```ts twoslash\nimport http from 'http'\nimport { createServer } from 'vite'\n\nconst parentServer = http.createServer() // or express, koa, etc.\n\nconst vite = await createServer({\n server: {\n // Enable middleware mode\n middlewareMode: {\n // Provide the parent http server for proxy WebSocket\n server: parentServer,\n },\n proxy: {\n '/ws': {\n target: 'ws://localhost:3000',\n // Proxying WebSocket\n ws: true,\n },\n },\n },\n})\n\n// @noErrors: 2339\nparentServer.use(vite.middlewares)\n```\n\nVite is running in %MODE%
\nUsing data from %VITE_API_URL%
\n```\n\nIf the env doesn't exist in `import.meta.env`, e.g. `%NON_EXISTENT%`, it will be ignored and not replaced, unlike `import.meta.env.NON_EXISTENT` in JS where it's replaced as `undefined`.\n\nGiven that Vite is used by many frameworks, it is intentionally unopinionated about complex replacements like conditionals. Vite can be extended using [an existing userland plugin](https://github.com/vitejs/awesome-vite#transformers) or a custom plugin that implements the [`transformIndexHtml` hook](./api-plugin#transformindexhtml).\n\n## Modes\n\nBy default, the dev server (`dev` command) runs in `development` mode and the `build` command runs in `production` mode.\n\nThis means when running `vite build`, it will load the env variables from `.env.production` if there is one:\n\n```[.env.production]\nVITE_APP_TITLE=My App\n```\n\nIn your app, you can render the title using `import.meta.env.VITE_APP_TITLE`.\n\nIn some cases, you may want to run `vite build` with a different mode to render a different title. You can overwrite the default mode used for a command by passing the `--mode` option flag. For example, if you want to build your app for a staging mode:\n\n```bash\nvite build --mode staging\n```\n\nAnd create a `.env.staging` file:\n\n```[.env.staging]\nVITE_APP_TITLE=My App (staging)\n```\n\nAs `vite build` runs a production build by default, you can also change this and run a development build by using a different mode and `.env` file configuration:\n\n```[.env.testing]\nNODE_ENV=development\n```\n\n### NODE_ENV and Modes\n\nIt's important to note that `NODE_ENV` (`process.env.NODE_ENV`) and modes are two different concepts. Here's how different commands affect the `NODE_ENV` and mode:\n\n| Command | NODE_ENV | Mode |\n| ---------------------------------------------------- | --------------- | --------------- |\n| `vite build` | `\"production\"` | `\"production\"` |\n| `vite build --mode development` | `\"production\"` | `\"development\"` |\n| `NODE_ENV=development vite build` | `\"development\"` | `\"production\"` |\n| `NODE_ENV=development vite build --mode development` | `\"development\"` | `\"development\"` |\n\nThe different values of `NODE_ENV` and mode also reflect on its corresponding `import.meta.env` properties:\n\n| Command | `import.meta.env.PROD` | `import.meta.env.DEV` |\n| ---------------------- | ---------------------- | --------------------- |\n| `NODE_ENV=production` | `true` | `false` |\n| `NODE_ENV=development` | `false` | `true` |\n| `NODE_ENV=other` | `false` | `true` |\n\n| Command | `import.meta.env.MODE` |\n| -------------------- | ---------------------- |\n| `--mode production` | `\"production\"` |\n| `--mode development` | `\"development\"` |\n| `--mode staging` | `\"staging\"` |\n\n:::tip `NODE_ENV` in `.env` files\n\n`NODE_ENV=...` can be set in the command, and also in your `.env` file. If `NODE_ENV` is specified in a `.env.[mode]` file, the mode can be used to control its value. However, both `NODE_ENV` and modes remain as two different concepts.\n\nThe main benefit with `NODE_ENV=...` in the command is that it allows Vite to detect the value early. It also allows you to read `process.env.NODE_ENV` in your Vite config as Vite can only load the env files once the config is evaluated.\n:::\n" }, { "path": "docs/guide/features.md", "content": "# Features\n\nAt the very basic level, developing using Vite is not that different from using a static file server. However, Vite provides many enhancements over native ESM imports to support various features that are typically seen in bundler-based setups.\n\n## npm Dependency Resolving and Pre-Bundling\n\nNative ES imports do not support bare module imports like the following:\n\n```js\nimport { someMethod } from 'my-dep'\n```\n\nThe above import will throw an error in the browser. Vite will detect such bare module imports in all served source files and perform the following:\n\n1. [Pre-bundle](./dep-pre-bundling) them to improve page loading speed and convert CommonJS / UMD modules to ESM. The pre-bundling step is performed with [esbuild](https://esbuild.github.io/) and makes Vite's cold start time significantly faster than any JavaScript-based bundler.\n\n2. Rewrite the imports to valid URLs like `/node_modules/.vite/deps/my-dep.js?v=f3sf2ebd` so that the browser can import them properly.\n\n**Dependencies are Strongly Cached**\n\nVite caches dependency requests via HTTP headers, so if you wish to locally edit/debug a dependency, follow the steps [here](./dep-pre-bundling#browser-cache).\n\n## Hot Module Replacement\n\nVite provides an [HMR API](./api-hmr) over native ESM. Frameworks with HMR capabilities can leverage the API to provide instant, precise updates without reloading the page or blowing away application state. Vite provides first-party HMR integrations for [Vue Single File Components](https://github.com/vitejs/vite-plugin-vue/tree/main/packages/plugin-vue) and [React Fast Refresh](https://github.com/vitejs/vite-plugin-react/tree/main/packages/plugin-react). There are also official integrations for Preact via [@prefresh/vite](https://github.com/JoviDeCroock/prefresh/tree/main/packages/vite).\n\nNote you don't need to manually set these up - when you [create an app via `create-vite`](./), the selected templates would have these pre-configured for you already.\n\n## TypeScript\n\nVite supports importing `.ts` files out of the box.\n\n### Transpile Only\n\nNote that Vite only performs transpilation on `.ts` files and does **NOT** perform type checking. It assumes type checking is taken care of by your IDE and build process.\n\nThe reason Vite does not perform type checking as part of the transform process is because the two jobs work fundamentally differently. Transpilation can work on a per-file basis and aligns perfectly with Vite's on-demand compile model. In comparison, type checking requires knowledge of the entire module graph. Shoe-horning type checking into Vite's transform pipeline will inevitably compromise Vite's speed benefits.\n\nVite's job is to get your source modules into a form that can run in the browser as fast as possible. To that end, we recommend separating static analysis checks from Vite's transform pipeline. This principle applies to other static analysis checks such as ESLint.\n\n- For production builds, you can run `tsc --noEmit` in addition to Vite's build command.\n\n- During development, if you need more than IDE hints, we recommend running `tsc --noEmit --watch` in a separate process, or use [vite-plugin-checker](https://github.com/fi3ework/vite-plugin-checker) if you prefer having type errors directly reported in the browser.\n\nVite uses [esbuild](https://github.com/evanw/esbuild) to transpile TypeScript into JavaScript which is about 20~30x faster than vanilla `tsc`, and HMR updates can reflect in the browser in under 50ms.\n\nUse the [Type-Only Imports and Export](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-8.html#type-only-imports-and-export) syntax to avoid potential problems like type-only imports being incorrectly bundled, for example:\n\n```ts\nimport type { T } from 'only/types'\nexport type { T }\n```\n\n### TypeScript Compiler Options\n\nVite respects some of the options in `tsconfig.json` and sets the corresponding esbuild options. For each file, Vite uses the `tsconfig.json` in the closest parent directory. If that `tsconfig.json` contains a [`references`](https://www.typescriptlang.org/tsconfig/#references) field, Vite will use the referenced config file that satisfies the [`include`](https://www.typescriptlang.org/tsconfig/#include) and [`exclude`](https://www.typescriptlang.org/tsconfig/#exclude) fields.\n\nWhen the options are set in both the Vite config and the `tsconfig.json`, the value in the Vite config takes precedence.\n\nSome configuration fields under `compilerOptions` in `tsconfig.json` require special attention.\n\n#### `isolatedModules`\n\n- [TypeScript documentation](https://www.typescriptlang.org/tsconfig#isolatedModules)\n\nShould be set to `true`.\n\nIt is because `esbuild` only performs transpilation without type information, it doesn't support certain features like const enum and implicit type-only imports.\n\nYou must set `\"isolatedModules\": true` in your `tsconfig.json` under `compilerOptions`, so that TS will warn you against the features that do not work with isolated transpilation.\n\nIf a dependency doesn't work well with `\"isolatedModules\": true`, you can use `\"skipLibCheck\": true` to temporarily suppress the errors until it is fixed upstream.\n\n#### `useDefineForClassFields`\n\n- [TypeScript documentation](https://www.typescriptlang.org/tsconfig#useDefineForClassFields)\n\nThe default value will be `true` if the TypeScript target is `ES2022` or newer including `ESNext`. It is consistent with the [behavior of TypeScript 4.3.2+](https://github.com/microsoft/TypeScript/pull/42663).\nOther TypeScript targets will default to `false`.\n\n`true` is the standard ECMAScript runtime behavior.\n\nIf you are using a library that heavily relies on class fields, please be careful about the library's intended usage of it.\nWhile most libraries expect `\"useDefineForClassFields\": true`, you can explicitly set `useDefineForClassFields` to `false` if your library doesn't support it.\n\n#### `target`\n\n- [TypeScript documentation](https://www.typescriptlang.org/tsconfig#target)\n\nVite ignores the `target` value in the `tsconfig.json`, following the same behavior as `esbuild`.\n\nTo specify the target in dev, the [`esbuild.target`](/config/shared-options.html#esbuild) option can be used, which defaults to `esnext` for minimal transpilation. In builds, the [`build.target`](/config/build-options.html#build-target) option takes higher priority over `esbuild.target` and can also be set if needed.\n\n#### `emitDecoratorMetadata`\n\n- [TypeScript documentation](https://www.typescriptlang.org/tsconfig#emitDecoratorMetadata)\n\nThis option is only partially supported. Full support requires type inference by the TypeScript compiler, which is not supported. See [Oxc Transformer's documentation](https://oxc.rs/docs/guide/usage/transformer/typescript#decorators) for details.\n\n#### `paths`\n\n- [TypeScript documentation](https://www.typescriptlang.org/tsconfig/#paths)\n\n`resolve.tsconfigPaths: true` can be specified to tell Vite to use the `paths` option in `tsconfig.json` to resolve imports.\n\nNote that this feature has a performance cost and is [discouraged by the TypeScript team to use this option to change the behavior of the external tools](https://www.typescriptlang.org/tsconfig/#paths:~:text=Note%20that%20this%20feature%20does%20not%20change%20how%20import%20paths%20are%20emitted%20by%20tsc%2C%20so%20paths%20should%20only%20be%20used%20to%20inform%20TypeScript%20that%20another%20tool%20has%20this%20mapping%20and%20will%20use%20it%20at%20runtime%20or%20when%20bundling.).\n\n#### Other Compiler Options Affecting the Build Result\n\n- [`extends`](https://www.typescriptlang.org/tsconfig#extends)\n- [`importsNotUsedAsValues`](https://www.typescriptlang.org/tsconfig#importsNotUsedAsValues)\n- [`preserveValueImports`](https://www.typescriptlang.org/tsconfig#preserveValueImports)\n- [`verbatimModuleSyntax`](https://www.typescriptlang.org/tsconfig#verbatimModuleSyntax)\n- [`jsx`](https://www.typescriptlang.org/tsconfig#jsx)\n- [`jsxFactory`](https://www.typescriptlang.org/tsconfig#jsxFactory)\n- [`jsxFragmentFactory`](https://www.typescriptlang.org/tsconfig#jsxFragmentFactory)\n- [`jsxImportSource`](https://www.typescriptlang.org/tsconfig#jsxImportSource)\n- [`experimentalDecorators`](https://www.typescriptlang.org/tsconfig#experimentalDecorators)\n\n::: tip `skipLibCheck`\nVite starter templates have `\"skipLibCheck\": \"true\"` by default to avoid typechecking dependencies, as they may choose to only support specific versions and configurations of TypeScript. You can learn more at [vuejs/vue-cli#5688](https://github.com/vuejs/vue-cli/pull/5688).\n:::\n\n### Client Types\n\nVite's default types are for its Node.js API. To shim the environment of client-side code in a Vite application, you can add `vite/client` to `compilerOptions.types` inside `tsconfig.json`:\n\n```json [tsconfig.json]\n{\n \"compilerOptions\": {\n \"types\": [\"vite/client\", \"some-other-global-lib\"]\n }\n}\n```\n\nNote that if [`compilerOptions.types`](https://www.typescriptlang.org/tsconfig#types) is specified, only these packages will be included in the global scope (instead of all visible ”@types” packages). This is recommended since TS 5.9.\n\n::: details Using triple-slash directive\n\nAlternatively, you can add a `d.ts` declaration file:\n\n```typescript [vite-env.d.ts]\n///