Vite 8.0.0-beta.7

Native-ESM powered web dev build tool

vite@8.0.0-beta.7 was published on 2026-01-08. Its manifest declares 7 runtime dependencies and 11 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is ^20.19.0 || >=22.12.0.

All Vite versions · Permanent reference to 8.0.0-beta.7 · Latest release

Package specifications

Version8.0.0-beta.7
License declarationMIT
Published2026-01-08T01:50:33.015Z
Node.js requirement^20.19.0 || >=22.12.0
Type declarationsBundled declarations
Runtime dependency count7
Peer requirement count11
Optional dependency count1
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size2177.71 KiB
Published file count42
Package typemodule
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies41
Repository stars83496
Repository forks8874

Install Vite 8.0.0-beta.7

npm install vite@8.0.0-beta.7
pnpm add vite@8.0.0-beta.7
yarn add vite@8.0.0-beta.7

Runtime dependencies

Peer requirements

  • tsx ^4.8.1 (optional peer)
  • jiti >=1.21.0 (optional peer)
  • less ^4.0.0 (optional peer)
  • sass ^1.70.0 (optional peer)
  • yaml ^2.4.2 (optional peer)
  • stylus >=0.54.8 (optional peer)
  • terser ^5.16.0 (optional peer)
  • esbuild ^0.25.0 (optional peer)
  • sugarss ^5.0.0 (optional peer)
  • @types/node ^20.19.0 || >=22.12.0 (optional peer)
  • sass-embedded ^1.70.0 (optional peer)

Optional dependencies

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained10/10 — 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Code-Review7/10 — Found 19/27 approved changesets -- score normalized to 7
Security-Policy10/10 — security policy file detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions7/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts1/10 — binaries present in source code
License10/10 — license file detected
Pinned-Dependencies6/10 — dependency not pinned by hash detected -- score normalized to 6
Fuzzing0/10 — project is not fuzzed
SAST10/10 — SAST tool is run on all commits

Compare Vite

Evidence and freshness