chore(deps): update dependency vite-plus to v0.2.8 - #36
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
|
All alerts resolved. Learn more about Socket for GitHub. This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. |
renovate
Bot
force-pushed
the
renovate/vite+
branch
from
July 7, 2026 17:40
767f027 to
61987de
Compare
renovate
Bot
force-pushed
the
renovate/vite+
branch
4 times, most recently
from
July 8, 2026 10:15
71cad5b to
067e96d
Compare
renovate
Bot
force-pushed
the
renovate/vite+
branch
from
July 12, 2026 12:31
067e96d to
5b28939
Compare
renovate
Bot
force-pushed
the
renovate/vite+
branch
from
July 17, 2026 11:17
5b28939 to
c6440ea
Compare
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
renovate
Bot
force-pushed
the
renovate/vite+
branch
from
July 23, 2026 08:40
c6440ea to
0847d89
Compare
renovate
Bot
force-pushed
the
renovate/vite+
branch
from
July 31, 2026 16:30
0847d89 to
7b51636
Compare
renovate
Bot
force-pushed
the
renovate/vite+
branch
from
August 5, 2026 10:17
7b51636 to
bbb5ca4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.2.1→0.2.8Release Notes
voidzero-dev/vite-plus (vite-plus)
v0.2.8: vite-plus v0.2.8: monorepo target resolution, breaking VP_* environment variable renames, and install fixesCompare Source
Bare
vp dev/build/preview/packat a monorepo root now resolve a target package instead of silently running against the root, and three Vite+-specific environment variables move to theVP_*prefix without compatibility aliases. Two failures that broke Vite+ before it could run are also fixed: the crash on container images that ship no CA certificates, and the missing Rolldown binding under pnpm's global virtual store.Breaking Changes
Rename three Vite+-specific environment variables to the
VP_*prefix, with no compatibility aliases, so the old names stop working (#2312), by @jong-kyung:VITE_LOGVP_LOGVITE_GLOBAL_CLI_JS_SCRIPTS_DIRVP_GLOBAL_CLI_JS_SCRIPTS_DIRVITE_UPDATE_TASK_TYPESVP_UPDATE_TASK_TYPESUpdate any shell profile, CI job, or Dockerfile that sets the old names.
Highlights
vp dev,build,preview, andpackat a monorepo root: interactive shells get a fuzzy package picker, non-interactive runs list the candidates and exit 1 instead of building the root, and a new global-C <dir>flag or adefaultPackagesetting (a single directory, or an object mapping each of the four commands to its own directory) skips the prompt (#2031, #2305), by @fengmk2vite-plus, fixingCannot find module 'vite-plus/binding'under pnpmenable-global-virtual-storeand in standalone@voidzero-dev/vite-plus-coreinstalls (#2313), by @fengmk2vp pm cifor reproducible frozen-lockfile installs, andvp pm patch/vp pm patch-commitfor editing dependencies in place on pnpm, bun, and Yarn Berry (npm and Yarn Classic warn and exit successfully) (#2082, #2308), by @forehalo and @jong-kyungFeatures
8.1.5->8.2.0, rolldown1.2.0->1.2.2, oxlint1.75.0->1.76.0, oxfmt0.60.0->0.61.0, and Vite DevTools0.4.5->0.4.10(#2302, #2311), by @voidzero-guard[bot]. The new oxfmt and oxlint can flag code that passed before, so runvp fmtafter upgrading if your CI runsvp check..nvmrcwhen no other version source is present (#2244), by @BlankParticle@pnpm/exe.*package and generates native shims, sopnpmandpnpxwork instead of failing to exec (#2289), by @jong-kyungdist.integrityhash (#2310), by @jong-kyungFixes & Enhancements
vp configinstall the Git hook dispatcher without creating or modifying project hook scripts or staged-file configuration, so a custom.vite-hooks/pre-commitsurvives (#2280), by @TheAlexLichterpackages/<package>/<uuid>instead of using#in the path, which Node treated as a URL fragment and which broke dynamic imports inside installed packages (#2222), by @liangmiQwQvp update -gfollows a dist tag or range instead of silently resolving back tolatest,vp outdated -greports Wanted versus Latest, andvp update -g --latestexplicitly moves packages back tolatest(#2249), by @TheAlexLichtervp create --package-manageroutside monorepos instead of inheriting the manager from a non-monorepo ancestor directory (#2226), by @jong-kyungvite:librarytemplate into a directory that contains only.git, while still refusing to overwrite existing user files (#2287), by @RSS1102vp <command> --helpmatches the installed toolchain instead of drifting (#2184), by @liangmiQwQtypeAwareandtypeCheckoptions inherited through Oxlintextends, sovp check --no-lintruns and classifies type checking correctly (#2228), by @jong-kyung(no version)instead ofunknownwhen globally installing a local package that has noversionfield (#2232), by @liangmiQwQRefactor
VP_GIT_HOOKS, keepingVITE_GIT_HOOKSworking as a deprecated alias (#2195), by @dennybiasiolliDocs
vpinstallation step in the onboarding prompt (#2291), by @Arcadi4Chore
vite-pluspeer of oxfmt and oxlint on every install (#2321), by @fengmk2@emnapipeers where@napi-rs/cliis used (#2319), by @jong-kyungrollup-testsfrom the workspace and updatebasic-ftp(#2322), by @fengmk2EnvConfigfields (#2320), by @jong-kyungvpprocess, and kill it before its children, in theenv_install_interruptsnapshot test (#2299, #2316), by @fengmk2vitest_browser_modesnapshot test (#2297), by @fengmk2Bundled Versions
8.2.0fa79f9a1.2.2872b98a0.22.144.1.101.76.07.0.20010.61.0Upgrade
New Contributors
@jbmusso, @Arcadi4, @dennybiasiolli, @RSS1102
Full Changelog: voidzero-dev/vite-plus@v0.2.7...v0.2.8
Published Packages
@voidzero-dev/vite-plus-core@0.2.8vite-plus@0.2.8Installation
macOS/Linux:
curl -fsSL https://vite.plus | bashWindows:
Or download and run
vp-setup.exefrom the assets below.Docker:
docker run --rm -it -v "$PWD:/app" -w /app ghcr.io/voidzero-dev/vite-plus:0.2.8 vp buildRun any
vpcommand without installing it; see the Docker guide for more.v0.2.7: vite-plus v0.2.7: Clearer guidance for built-in commands and scriptsCompare Source
This release points users to
vpr <name>when a Vite+ built-in command and package script share a name, adds concurrency control tovp pack, and smooths migrations and package-manager setup.Highlights
vpr <name>when a Vite+ built-in command andpackage.jsonscript share a name (#2259, #2262, #2265, vite-task#570), by @wan9chi--concurrencytovp packto limit parallel Rolldown builds, and update tsdown0.22.13->0.22.14and Vite DevTools0.4.2->0.4.5(#2233), by @voidzero-guard[bot]no-undeferrors (#2192), by @naokihabaFixes & Enhancements
Docs
vpcommands versus package scripts throughvp runorvpr, including migration and agent guidance (#2255), by @wan9chisetup-vptemplate (#2258), by @naokihabaChore
main(#2223), by @Boshenjs/ts.*names (#2246), by @jong-kyungBundled Versions
8.1.55e7fe121.2.003e1e340.22.144.1.101.75.07.0.20010.60.0Upgrade
Full Changelog: voidzero-dev/vite-plus@v0.2.6...v0.2.7
Published Packages
@voidzero-dev/vite-plus-core@0.2.7vite-plus@0.2.7Installation
macOS/Linux:
curl -fsSL https://vite.plus | bashWindows:
Or download and run
vp-setup.exefrom the assets below.View the full commit:
c17e1c3Docker:
docker run --rm -it -v "$PWD:/app" -w /app ghcr.io/voidzero-dev/vite-plus:0.2.7 vp buildRun any
vpcommand without installing it; see the Docker guide for more.v0.2.6: vite-plus v0.2.6: Stable type-aware linting and more reliable task cachingCompare Source
This release moves Vite+'s type-aware linting to the stable tsgolint 7 engine, updates the bundled build and formatting tools, strengthens
vp runcaching and workspace discovery, and removes the redundantvp buildstartup banner.Highlights
8.1.4->8.1.5, Rolldown1.1.5->1.2.0, tsdown0.22.7->0.22.13, Oxlint1.73.0->1.75.0, oxlint-tsgolint0.24.0->7.0.2001, and Oxfmt0.58.0->0.60.0(#2214), by @voidzero-guard[bot]vp runreliability by caching much larger automatically tracked input sets, discovering npm workspaces whose patterns start with./, and providing more accurate error messages (vite-task#554, vite-task#547, vite-task#552, #2215), by @wan9chi and @liangmiQwQvp buildoutput and fail fast when upstream Vite changes invalidate Vite+ branding patches (#2200, #2205), by @liangmiQwQRefactor
Docs
Chore
vp createbuild-approval snapshots by removing package-age timing from those fixtures (#2224), by @wan9chiBundled Versions
8.1.55e7fe121.2.003e1e340.22.134.1.101.75.07.0.20010.60.0Upgrade
New Contributors
Welcome @charpeni.
Full Changelog: voidzero-dev/vite-plus@v0.2.5...v0.2.6
Published Packages
@voidzero-dev/vite-plus-core@0.2.6vite-plus@0.2.6Installation
macOS/Linux:
curl -fsSL https://vite.plus | bashWindows:
Or download and run
vp-setup.exefrom the assets below.View the full commit:
cd064c6Docker:
docker run --rm -it -v "$PWD:/app" -w /app ghcr.io/voidzero-dev/vite-plus:0.2.6 vp buildRun any
vpcommand without installing it; see the Docker guide for more.v0.2.5: vite-plus v0.2.5: Cleaner environments and more reliable workflowsCompare Source
This release adds cleanup and package version commands, supports TypeScript 7 declaration generation, reduces the standalone binary size, and hardens task tracking, CLI output, package-manager routing, Docker workflows, and project scaffolding.
Highlights
vp env cleanto remove unused managed Node.js runtimes and package-manager caches (#2003), by @liangmiQwQvp pm version, forwarding native version commands to npm, pnpm, Yarn, and Bun (#2127), by @jong-kyung0.22.7(#2104, #2168), by @wan9chi/dev/shm, and Windows process images, reduce Windows backing-file allocation, and clarify task wait failures (vite-task#515, vite-task#518, vite-task#523, vite-task#524, vite-task#542, #2126, #2167), by @wan9chiFixes & Enhancements
vpbinary sizes by about 5% on Linux and macOS and 19% on Windows (#2043), by @fengmk2sudofor Playwright browser dependencies and system packages (#2088), by @fengmk2.envand.env.*in generated projects while keeping.env.exampletrackable (#2095), by @forehalovp-use.cmdafter the Windows environment bin directory is ready and document its Command Prompt-only usage (#2128), by @liangmiQwQvp dedupefall back toyarn installwith a warning on Yarn Classic (#2139), by @jong-kyungDocs
CONTRIBUTING.mdas Bash code blocks (#2159), by @BlankParticleChore
Bundled Versions
8.1.4a4774541.1.5f09947a0.22.74.1.101.73.00.24.00.58.0Upgrade
New Contributors
Welcome @yukinoshi and @BlankParticle.
Full Changelog: voidzero-dev/vite-plus@v0.2.4...v0.2.5
Published Packages
@voidzero-dev/vite-plus-core@0.2.5vite-plus@0.2.5Installation
macOS/Linux:
curl -fsSL https://vite.plus | bashWindows:
Or download and run
vp-setup.exefrom the assets below.View the full commit:
93dc59aDocker:
docker run --rm -it -v "$PWD:/app" -w /app ghcr.io/voidzero-dev/vite-plus:0.2.5 vp buildRun any
vpcommand without installing it; see the Docker guide for more.v0.2.4: vite-plus v0.2.4: Vitest security hotfixCompare Source
This hotfix updates the bundled Vitest Browser Mode packages to
4.1.10, which includes the fix for GHSA-p63j-vcc4-9vmv. The advisory is critical and affects@vitest/browser <=4.1.9.Highlights
vitestand@vitest/browser*move from4.1.9to4.1.10, addressing GHSA-p63j-vcc4-9vmv, where provider commands could bypass the file access permission gate (#2089), by @voidzero-guard[bot]Chore
Bundled Versions
8.1.3578ffb81.1.46cbd2330.22.34.1.101.72.00.24.00.57.0Upgrade
New Contributors
No new contributors in this release.
Full Changelog: voidzero-dev/vite-plus@v0.2.3...v0.2.4
Published Packages
@voidzero-dev/vite-plus-core@0.2.4vite-plus@0.2.4Installation
macOS/Linux:
curl -fsSL https://vite.plus | bashWindows:
Or download and run
vp-setup.exefrom the assets below.Docker:
docker run --rm -it -v "$PWD:/app" -w /app ghcr.io/voidzero-dev/vite-plus:0.2.4 vp buildRun any
vpcommand without installing it; see the Docker guide for more.v0.2.3: vite-plus v0.2.3: config extraction, create, and vp run reliability fixesCompare Source
A patch release that fixes static config extraction for
vite.config.tsfiles whosedefineConfigcomes from a preset or custom wrapper (no longer misread as Vite+'s own), fixesvp createfor org templates on registries that strip custom package fields, cleans up terminal output after Ctrl-C duringvp run, and updates bundled Vite to 8.1.3.Highlights
VP_HOMEis honored on every run: the globalvpnow respects a user-setVP_HOMEfor its home directory instead of falling back to~/.vite-plus, and persists it in the generated env files, so a custom install location no longer produces multiple instances or unusable packages (#2029), by @liangmiQwQFeatures
8.1.2to8.1.3(inlined CSS after the shebang line, CSS preload for nested dynamic imports, SSR stacktrace column fix) (#2042), by @voidzero-guard[bot]Fixes & Enhancements
vp runno longer misreads avite.config.tswhen itsdefineConfigcomes from a preset or a custom wrapper instead ofvite-plusorvite. Such configs are now evaluated at runtime rather than assumed to be Vite+'s own, so projects that use them no longer wrongly reportTask "build" not found(#2060, #2075), by @liangmiQwQ and @fengmk2vp runtask with Ctrl-C no longer leaves odd OSC escape sequences in the terminal;vpdefers its own Ctrl-C handling until the child process exits (#2079), by @forehalovp migrate: rewriting apackage.jsonprettier script now emits a single--check, so scripts that combined--checkwith--list-different/-l/-cno longer produce a duplicatedvp fmt --check --check(#2044), by @shulaodavp create @org:name: read the org template catalog (createConfig) from the published tarball when the registry (e.g. GitHub Packages) strips custom fields from packument metadata (#2063), by @hiro-daikinvp run: missing env vars requested through@voidzero-dev/vite-task-clientnow returnundefinedinstead ofnull, preserving Vite productionNODE_ENVsemantics when builds run throughvp run(vite-task#508, via #2076), by @wan9chiRefactor
static_config: drop the unreachablevite.config.jsonbranch (#2045), and remove unused exported CLI helpers (#2046), by @shulaodaDocs
Dockerfile.alpinecomment (#2068), by @fengmk2pnpm-workspace.yamlto the docs Dockerfile (#2059), by @wan-kongChore
vp runoutput for docs builds (#2006), by @wan9chiBundled Versions
8.1.3578ffb81.1.46cbd2330.22.34.1.91.72.00.24.00.57.0Upgrade
New Contributors
@wan-kong and @hiro-daikin made their first contributions.
Full Changelog: voidzero-dev/vite-plus@v0.2.2...v0.2.3
Published Packages
@voidzero-dev/vite-plus-core@0.2.3vite-plus@0.2.3Installation
macOS/Linux:
curl -fsSL https://vite.plus | bashWindows:
Or download and run
vp-setup.exefrom the assets below.Docker:
docker run --rm -it -v "$PWD:/app" -w /app ghcr.io/voidzero-dev/vite-plus:0.2.3 vp buildRun any
vpcommand without installing it; see the Docker guide for more.v0.2.2: vite-plus v0.2.2: Vite+ BetaCompare Source
Vite+ is now in Beta: stable and ready for production adoption, fully open source under MIT. Read the announcement to see what Vite+ is about and where it is headed: Announcing Vite+ Beta.
On top of the Beta milestone, this release brings cross-version upgrades via
vp migrate, an official Docker toolchain image on GHCR, zero-config runner-awarevp buildcaching, and PGP-verified managed Node.js downloads.Highlights
vp migrateupgrades existing Vite+ projects across versions: previous release notes told users not to runvp migratefor upgrades. It now runs from the global CLI when the local one is older, re-pinsvite-plusand thevite->@voidzero-dev/vite-plus-corealias across dependencies, overrides/resolutions, and catalogs in every workspace package, alignsvitest/@vitest/*by actual usage, and defaults to a version-only upgrade (pass--fullto also run the first-time setup bucket: hooks, editor, agent files, lint migration) (#1891), by @fengmk2ghcr.io/voidzero-dev/vite-plusbundlesvpplus a native build toolchain ondebian:bookworm-slim(amd64/arm64, non-root). Sincevpprovisions the exact Node.js from.node-version, one image builds any project, and a documented multi-stage build copies the resolved Node.js into a small vp-free runtime stage (#1944), by @fengmk2vp buildcaching via runner-aware Vite: Vite reports its inputs, outputs, and tracked env reads to thevprunner over the new@voidzero-dev/vite-task-clientIPC (vite#22453), sovp buildcaches correctly with no hand-written cache config: outputs are tracked and restored automatically, and a changedVITE_*env var invalidates the cache and is named in the cache-miss message (#1774), by @wan9chiSHASUMS256.txt.ascagainst the vendored Node.js release keyring (pure Rust, nogpgrequired) before trusting any checksum, so a tampered archive is rejected before install; unsigned sources (musl builds, custom mirrors) fall back to checksum-only verification (#1848), by @fengmk2Features
vp check: acheckblock invite.config.ts(check.fmt/check.lint) can make plainvp checkskip formatting or linting by default, mirroring--no-fmt/--no-lint; standalonevp fmt/vp lintand git hooks are unaffected, and anote:line keeps the config-based skip discoverable (#1981), by @fengmk2vp env list-remote: highlight installed versions (color, or a*prefix when piped) and label the project-resolvedcurrentand globaldefaultversions;--jsongainsinstalled/current/defaultfields (#1907), by @semimikohvprships as avite-pluspackage bin, so thevp runshorthand works on clean installs without global PATH shims (Vercel build image, generic CI runners) (#1988), by @kvnwolfdependsOncan select tasks from dependency packages, e.g.dependsOn: [{ "task": "build", "from": "dependencies" }](vite-task#479), by @wan9chienv/untrackedEnvglob patterns support!negation (e.g.["VITE_*", "!VITE_SECRET"]) (vite-task#425), and an env-caused cache miss now names the variable inline, e.g.cache miss: env 'NODE_ENV' changed(vite-task#438), by @wan9chi8.0.16 -> 8.1.2, rolldown1.1.1 -> 1.1.4, oxlint1.70.0 -> 1.72.0, oxfmt0.55.0 -> 0.57.0, oxlint-tsgolint0.23.0 -> 0.24.0, and the oxc toolchain0.136.0 -> 0.138.0(#1924, #1989, #2000, #2009), by @voidzero-guard[bot]Fixes & Enhancements
vp runno longer hangs CI when anode_modules/.bin.cmdshim is routed through PowerShell; the npm/pnpm/yarn.ps1wrappers read stdin and block forever on a non-TTY pipe, so the PowerShell rewrite is now skipped when stdin is not an interactive terminal (vite-task#491, via #1973), by @fengmk2node_modules/.vite/task-cache/v13/), so switching between branches that pin different Vite+ versions no longer fails withUnrecognized database version(vite-task#433), by @fengmk2PATH=... commandnow affect executable lookup during planning (vite-task#440);package.json/pnpm-workspace.yamlfiles with a UTF-8 BOM parse correctly (vite-task#424), by @wan9chivp upgrade: run the pinned pnpm with a managed Node.js LTS directly instead of re-enteringvp install, so an incompatible session/project/system runtime can no longer make pnpm skip optional native binaries and leave the upgraded CLI broken (#1900), by @liangmiQwQpackages/<name>#<uuid>prefix that is activated via metadata after npmConfiguration
📅 Schedule: (in timezone Asia/Shanghai)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.