vite

library1.5.2jsnpmunverified

Vite is a next-generation frontend build tool, currently at stable version 8.0.8, designed to significantly improve the frontend development experience. It functions as a dev server serving source files over native ES modules with fast Hot Module Replacement (HMR), and a build command that bundles code with Rollup for optimized production assets. Vite provides rich built-in features, a universal plugin interface, and fully typed APIs, making it highly extensible. Patch releases are frequent, with major versions released periodically.

web-framework

npm install vite

github ↗package ↗homepage ↗

INSTALL

IMPORT

SIG · VITE

vite

web-frameworkjavascriptv1.5.2

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

defineConfig

✓ import { defineConfig } from 'vite'

Primarily used for configuring vite.config.ts/js files.

This command creates a new Vite project using the `create-vite` scaffold, setting up a React project with TypeScript. It then navigates into the project directory, installs dependencies, and starts the development server.

npm create vite@latest my-vite-app -- --template react-ts cd my-vite-app npm install npm run dev

vite --version

Debug

Known issues

breakingVite requires Node.js version `^20.19.0` or `>=22.12.0`.

fix

Upgrade your Node.js installation to version 20.19.0 or higher, or 22.12.0 or higher.

affects: <8.0.0

gotchaVite configuration files (e.g., `vite.config.js`) must be written as native ES Modules (ESM).

fix

Ensure your configuration file uses `export default` for its primary export and ESM `import` statements. If using a `.js` file, ensure your project's `package.json` has `"type": "module"` or rename the config file to `vite.config.mjs`.

affects: >=2.0.0

gotchaEnvironment variables exposed to client-side code must be prefixed with `VITE_`.

fix

Rename your environment variables (e.g., `.env` file) to `VITE_MY_VAR` and access them via `import.meta.env.VITE_MY_VAR`.

affects: >=2.0.0

gotchaThe `esbuild` package is a peer dependency and is crucial for Vite's fast cold start and build performance. While Vite can fall back without it, it's highly recommended.

fix

Ensure `esbuild` is installed in your project: `npm install esbuild` or `yarn add esbuild` or `pnpm add esbuild`.

affects: >=2.0.0

gotchaFor supporting older browsers (e.g., IE11), the `@vitejs/plugin-legacy` plugin is required.

fix

Install the plugin (`npm install -D @vitejs/plugin-legacy`) and add it to your `vite.config.js` plugins array.

affects: >=2.0.0

Errors

Common errors & fixes

SyntaxError: Cannot use import statement outside a module

Attempting to use ESM syntax (like `import` and `export default`) in a Vite configuration file that is being treated as CommonJS.

fix

Ensure your `vite.config.js` file is interpreted as an ES Module. This can be done by adding `"type": "module"` to your `package.json` or by renaming `vite.config.js` to `vite.config.mjs`.

Your current Node.js version is [X]. Vite requires Node.js version ^20.19.0 || >=22.12.0.

The Node.js version running Vite does not meet the minimum requirements specified in the package's `engines` field.

fix

Upgrade your Node.js installation to version `^20.19.0` or `>=22.12.0`.

ReferenceError: process is not defined

Accessing `process.env` directly in client-side code, which is a Node.js global and not available in the browser environment.

fix

Use `import.meta.env` for environment variables in client-side code. For custom variables, ensure they are prefixed with `VITE_` (e.g., `VITE_APP_API_URL`).

Failed to resolve import "some-package" from "src/main.ts"

The imported module cannot be found in `node_modules`, its `package.json` `exports` field is misconfigured, or the import path is incorrect.

fix

Verify that `some-package` is installed correctly via `npm install some-package`. Check the module's documentation for correct import paths and ensure its `package.json` properly defines its exports for ESM environments.

RollupError: "SymbolName" is not exported by "module-name.js"

Attempting to import a named export that does not exist in the specified module, often due to incorrect CommonJS/ESM interop or misconfigured exports in a third-party library.

fix

Check the module's documentation or source code for available exports. Ensure named exports are correctly defined or consider using a default import if the module primarily uses default exports.

Upgrade

Version history

1.5.2latest on npm

Audit

Dependencies

No dependency data recorded yet.

Agent activity

20 hits · last 30 days

node

Resources

githubhttps://github.com/vitejs/vite ↗

packagehttps://www.npmjs.com/package/vite ↗

homepagehttps://vite.dev ↗