# Install vite with Homebrew, apt, Nix Next generation frontend tooling. It's fast! Version 8.1.3 via Homebrew; verified 2026-07-03. ## Install ```sh sudo av install brew:vite ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install vite ``` Evidence: local Homebrew formula metadata ### Linux - Debian apt (92%): ```sh sudo apt install vite ``` Evidence: Debian stable package indexes: vite from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz - Nix (92%): ```sh nix profile install nixpkgs#vite ``` Evidence: nixpkgs package indexes: pkgs/by-name/vi/vite/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Package facts - **Package key:** brew:vite - **Package manager:** Homebrew - **Package manager page:** - **Version:** 8.1.3 - **Source summary:** Next generation frontend tooling. It's fast! - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** MIT - **Source archive:** - **Last updated:** 2026-07-03T07:22:19Z - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - vite (cli) - vite (alias) ## Dependencies - node ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux ## Freshness - Page generated: 2026-07-08 - Package-manager version: 8.1.3 - Package-manager updated: 2026-07-03 - Local data: ok - Upstream repository: https://vitejs.dev/ - info: Release/tag comparison is only available for GitHub repositories. ## Project history and usage Vite is a frontend development server and build tool created by Evan You for the browser-native ES module era. Its central idea is to avoid rebuilding a whole application during development: source modules are served on demand, dependencies are pre-bundled, and hot updates travel through native ESM boundaries. In package-manager culture, Vite became the default small executable behind many JavaScript framework starters. The `vite` command is used both as an interactive development server and as the entry point for production builds, making it a common tool even for developers who encounter it indirectly through framework CLIs. ### Project history Vite emerged in 2020 as a response to the long startup and rebuild times of bundle-first JavaScript tooling. The official documentation frames its origins around the moment when browsers had gained broad ES module support, allowing development servers to let the browser load modules directly instead of constructing an entire bundle before first page load. Vite 2, released by Evan You in February 2021, was the point where the project became a broader framework-agnostic tool rather than only a Vue-oriented experiment. Later major releases focused on ecosystem stability, plugin compatibility, performance, and keeping the development and production pipelines aligned. By the mid-2020s, Vite's roadmap had shifted toward unifying more of the toolchain. Official Vite documentation describes the migration toward Rolldown so that dependency pre-bundling and production bundling can eventually share a high-performance Rollup-compatible foundation. ### Adoption history Vite adoption accelerated quickly after Vite 2. The Vite 3 announcement said the project had passed one million npm downloads per week and named Nuxt 3, SvelteKit, Astro, Hydrogen, and SolidStart as frameworks built with or defaulting to Vite. The Vite 4 announcement reported growth from one million to 2.5 million npm downloads per week, and the Vite 5 announcement reported a further jump to 7.5 million weekly downloads. These official release notes also positioned Vite as shared infrastructure for an expanding framework ecosystem rather than a single-framework companion. In 2026 the Vite project described a new stage after VoidZero joined Cloudflare, while stating that Vite remained open source, vendor-agnostic, and stewarded by the Vite team with members from multiple organizations and independent contributors. ### How it is used A typical Vite workflow starts a local development server, serves source files as native ESM, applies fast transforms, and sends HMR updates without forcing a full page reload. For production, Vite builds optimized assets through its bundling pipeline. Vite is also used as a plugin platform. Its Rollup-inspired plugin API, framework integrations, and configuration files make the `vite` package a common dependency in frontend apps, component libraries, documentation sites, and server-rendered web frameworks. ### Why package nerds care Vite matters to package nerds because it is both a visible CLI and a hidden ecosystem substrate. Installing a modern frontend starter often means installing Vite or a framework layer that delegates development and build behavior to Vite. It also marks a generational shift away from older dev-server assumptions: native ESM during development, aggressive dependency pre-bundling, and framework-shared tooling replaced many bespoke Webpack-era setups. ### Timeline - 2020: Vite was created in the period when native browser ES modules were broadly usable for development tooling. - 2021: Evan You released Vite 2, broadening Vite into a general-purpose frontend build tool. - 2022: Vite 3 reported more than one million npm downloads per week and a rapidly growing framework ecosystem. - 2022: Vite 4 reported growth to 2.5 million npm downloads per week. - 2023: Vite 5 reported growth to 7.5 million npm downloads per week and continued framework adoption. - 2025-2026: The official roadmap centered on Rolldown integration and a more unified JavaScript toolchain. - 2026: Vite announced that VoidZero was joining Cloudflare while keeping Vite open source and vendor-agnostic. ### Related projects - Vite is closely related to Rollup, esbuild, and Rolldown because those tools shape its plugin compatibility, dependency optimization, and production bundling story. - Frameworks and meta-frameworks named in official Vite release notes include Nuxt, SvelteKit, Astro, Hydrogen, SolidStart, Laravel, Rails integrations through Vite Ruby, and later Qwik City and other ecosystem entrants. ### Sources - batch input current_curation.repo, current_curation.docs, current_curation.tags, and current_curation.config-file-location - - - - - - - ## Security Notes No matching local secret-handling manifest was found for vite. Nucleus package metadata is still published here so future coverage has a stable package URL. ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: project root/vite.config.js, project root/vite.config.ts, project root/vite.config.mjs, project root/vite.config.mts - Windows: project root/vite.config.js, project root/vite.config.ts, project root/vite.config.mjs, project root/vite.config.mts ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** vite - **Version Scheme:** 0 - **Revision:** 0 - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** stable ## Other Package-Manager Records - Debian apt - vite - 1.4-1: normalized package name match | Debian stable package indexes: vite from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | Efficient visual trace explorer | https://solverstack.gitlabpages.inria.fr/vite/ - Nix - vite: normalized package name match | nixpkgs package indexes: pkgs/by-name/vi/vite/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - Ubuntu apt - vite - 1.2+svn+git4.c6c0ce7-8build2: normalized package name match | Ubuntu 24.04 LTS package indexes: vite from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | Efficient visual trace explorer | https://vite.gforge.inria.fr/ ## Related links - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Text processing packages](https://www.automicvault.com/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata. - [Developer build packages](https://www.automicvault.com/pkg/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata. - [Language runtime packages](https://www.automicvault.com/pkg/language-runtime-packages/) - Matched language runtime, compiler, or interpreter metadata. - [node](https://www.automicvault.com/pkg/brew/node/) - Runtime dependency declared by Homebrew. - [vite-plus](https://www.automicvault.com/pkg/brew/vite-plus/) - Shares av.db curated category or tags: build-tools, cli, developer-tools, frontend, javascript. - [nuxi](https://www.automicvault.com/pkg/brew/nuxi/) - Shares av.db curated category or tags: cli, developer-tools, javascript, typescript, web-development. - [webpack](https://www.automicvault.com/pkg/brew/webpack/) - Shares av.db curated category or tags: build-tool, build-tools, cli, developer-tools, frontend. - [angular-cli](https://www.automicvault.com/pkg/brew/angular-cli/) - Shares av.db curated category or tags: cli, developer-tools, javascript, web-development. - [esbuild](https://www.automicvault.com/pkg/brew/esbuild/) - Shares av.db curated category or tags: build-tools, cli, developer-tools, javascript, typescript. - [grunt-cli](https://www.automicvault.com/pkg/brew/grunt-cli/) - Shares av.db curated category or tags: build-tool, build-tools, cli, developer-tools, javascript. - [gwt](https://www.automicvault.com/pkg/brew/gwt/) - Shares av.db curated category or tags: cli, developer-tools, javascript, web-development. - [livereload](https://www.automicvault.com/pkg/brew/livereload/) - Shares av.db curated category or tags: cli, dev-server, developer-tools, web-development. - [vite](https://www.automicvault.com/pkg/npm/vite/) - Same normalized package name appears in another local ecosystem. Shared terms: build, build-tool, dev, dev-server, frontend. - [mako](https://www.automicvault.com/pkg/brew/mako/) - Both packages touch the same language runtime or ecosystem. Shared terms: build, build-tools, cli, developer, developer-tools. - [vite](https://www.automicvault.com/pkg/npm/vite/) - Same normalized package name in another local ecosystem. ## Combined YAML source View the package source record on GitHub. [combined/vite.yml](https://github.com/automic-vault/db/blob/main/combined/vite.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph