vite/

Docs

• config-server-options.md

  Unless noted, the options in this section are only applied to dev.

• config-shared-options.md

  Unless noted, the options in this section are applied to all dev, build, and preview.

• guide-api-plugin.md

  Vite plugins extends Rolldown's plugin interface with a few extra Vite-specific options. As a result, you can write a Vite plugin once and have it work for both dev and build.

• guide-build.md

  When it is time to deploy your app for production, simply run the vite build command. By default, it uses <root>/index.html as the build entry point, and produces an application bundle that is suitable to be served over a static hosting service. Check out the Deploying a Static Site for guides about popular services.

• guide-cli.md

  Dev server

• guide-env-and-mode.md

  Vite exposes certain constants under the special import.meta.env object. These constants are defined as global variables during dev and statically replaced at build time to make tree-shaking effective.

• guide-features.md

  At 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.

• guide-migration.md

  If you are migrating from rolldown-vite, the technical preview release for Rolldown integrated Vite for v6 & v7, only the sections with <Badge text="NRV" type="warning" /> in the title are applicable.

• guide-ssr.md

  :::tip Note SSR specifically refers to front-end frameworks (for example React, Preact, Vue, and Svelte) that support running the same application in Node.js, pre-rendering it to HTML, and finally hydrating it on the client. If you are looking for integration with traditional server-side frameworks, check out the Backend Integration guide instead.

• guide-troubleshooting.md

  See Rollup's troubleshooting guide for more information too.

Other files

LICENSE