/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

vitejs/vite

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T12:47:36.160Z

3mo ago

vitejs/vite

Vite is a very active, widely used frontend tooling monorepo with 79,437 stars and 7,967 forks. It focuses on fast dev startup, HMR, optimized production builds, and a typed plugin/API surface. The repo is current and actively maintained, with commits and dependency updates on 2026-03-30.

Loading tags...

Stars79,437

Forks7,967

Default branchmain

Last pushed2026-03-30T03:57:47Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Prefer this fork only if its custom build/CSS/SSR work matches a specific need you own and you are willing to maintain a diverged codebase. If you want the most stable, current, and broadly supported Vite, upstream is the better default.

Prefer upstream Vite unless you specifically need this fork’s custom runtime/build/workflow changes and are prepared to maintain a very old, highly divergent codebase yourself.

Prefer upstream Vite unless you specifically need this fork’s custom core behavior and are prepared to maintain a large divergence. This fork looks suitable for internal experimentation or a bespoke toolchain, but it is too stale and too far from upstream to be the safer default for general adoption.

Prefer this fork only if you need its snapshot-specific behavior or backports and are prepared to own the maintenance. If you want current Vite features, compatibility, and lower operational risk, upstream is the better choice.

Choose this fork only if you need its specific local changes and are prepared to own a stale, highly divergent codebase. For most adopters, upstream Vite is the safer default because this fork is materially behind and likely costlier to maintain.

Choose this fork only if you need its specific 2023-era customizations and are willing to own the maintenance burden. For most adopters, upstream Vite is the safer and more current choice.

Prefer this fork only if you specifically need its legacy behavior and are prepared to maintain it yourself; otherwise current upstream is the safer choice for features, fixes, and ecosystem compatibility.

Choose this fork only if you specifically need its customized 2024-era Vite state. For most adopters, upstream is the better choice because this fork is stale and far behind current fixes and releases.

Choose this fork only if you need its specific downstream changes and are prepared to maintain them yourself. For most adopters, upstream Vite is the better choice because it is active, current, and much lower risk to integrate.

Choose this fork only if you need its custom Vite internals and are prepared to maintain a large upstream gap. For most users, upstream Vite is the safer choice because it is far more current, actively maintained, and less risky to adopt.

Fork comparison

iKowalchuk/vite

38/100

stale

significant_divergence

Prefer this fork only if its custom build/CSS/SSR work matches a specific need you own and you are willing to maintain a diverged codebase. If you want the most stable, current, and broadly supported Vite, upstream is the better default.

Likely purpose

To customize Vite’s internals around build, CSS, optimizer, and SSR/HMR behavior, likely as an experimental or private integration branch rather than a general-purpose upstream replacement.

Best for

Teams already committed to a custom Vite variant.; Engineers experimenting with Rolldown or other build-pipeline changes.; Users who need internal Vite behavior tweaks and can own long-term maintenance.; Not a good fit for teams that just want the safest, most current Vite distribution.

Additional features

Changes in core build/config/optimizer internals suggest custom pipeline behavior beyond stock Vite.
Rolldown-related dependency updates indicate work toward or around an alternative bundling/build backend.
Optimizer logging for scans or bundling over 1s adds operational visibility for slow dependency analysis.
CSS pipeline changes suggest altered handling or optimization of styles.
SSR/HMR test changes suggest fork-specific fixes or behavior adjustments in server-side hot reloading.
Adds plugin, tool, or MCP-style extensibility beyond the upstream baseline.

Missing features

It appears materially behind upstream’s recent 2026 releases and dependency updates.
The fork likely misses newer upstream bugfixes and maintenance work landed after its last push in 2025.
Upstream’s current release and docs automation cadence is not reflected here, so adopters may have to backport fixes themselves.
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
Some upstream plugin, tool, or MCP-style integration paths may be reduced or disabled.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Large, focused changes across core Vite internals rather than superficial edits.
Potentially useful if you need custom build performance or alternate bundling behavior.
Could suit teams validating nonstandard Vite integration points before adopting upstream changes.

Risks

High divergence makes rebasing or merging upstream fixes expensive.
Stale activity increases the chance of unpatched bugs and ecosystem drift.
The fork may be harder to adopt for teams expecting stock Vite behavior, docs, and release cadence.
Some changes may be experimental and not production-hardened.