chore(deps): update vite+ to v0.2.0#33
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
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.1.24→0.2.0Release Notes
voidzero-dev/vite-plus (vite-plus)
v0.2.0: vite-plus v0.2.0Compare Source
Vite+ now consumes upstream Vitest directly (no wrapper), raises the minimum supported Node.js version to 22.18.0, and ships corepack and devEngines support.
Highlights
vp testnow runs upstream Vitest directly (breaking): Vite+ used to ship@voidzero-dev/vite-plus-test, a rebundled copy of Vitest that lagged upstream releases. That package is removed;vp testnow runs the real upstreamvitest, which is installed automatically as a dependency ofvite-plus(you no longer addvitestor@vitest/*yourself, andvitestill resolves to@voidzero-dev/vite-plus-corevia package-manager overrides). Yourimport ... from 'vite-plus/test'code keeps working unchanged andvp migrateupdates existing projects (#1588), by @Brooooooklyn^22.18.0 || >=24.11.0(breaking): Node 20 reached end-of-life and the bundled tsdown already required^22.18.0, so the published engines range now matches whatvp packcan actually deliver;vp exec/vp run/vp dlxreject projects resolving an older Node with the existing incompatibility error (#1813), by @fengmk2corepacknow set up by default, socorepack enableand the pnpm/yarn launchers just work, even on Node 25+ which no longer ships it. (#1808), by @fengmk2devEngines.runtime(ranked aboveengines.node) anddevEngines.packageManager; auto-pin andvp migratewritedevEngines.packageManager,vp env pin/unpintargetdevEngines.runtime, andvp env doctorreports conflicts instead of silently resolving them (#1760), by @fengmk2Features
vp pm approve-builds: forward to npm's newapprove-scripts/deny-scripts(npm >= 11.16.0) instead of the previous no-op, matchingpnpm approve-builds/bun pm trust; mixed approve+deny is rejected with actionable guidance and npm's advisory-only caveat is surfaced (#1733), by @fengmk2vp create: support local monorepo templates declared increate.templatesinvite.config.ts;vp create vite:generatorscaffolds a Bingo generator and auto-registers it in the picker, replacing the old package.json-keyword inference (#1777), by @fengmk2vp create: detect direct dependencies whose build scripts the package manager gated (e.g. native builds likebetter-sqlite3) and act on them; prompt to approve each (default off) interactively, point atvp pm approve-buildsnon-interactively, or build them with--approve-builds(#1828), by @fengmk2vp config: add--no-hooksand--no-agentopt-outs to skip git-hook installation and coding-agent instruction updates (#1842), by @leno23vp list -g: sort the global package list output so entries appear in a stable order (#1748), by @liangmiQwQ1.0.3 -> 1.1.1, tsdown0.22.1 -> 0.22.3, oxlint1.67.0 -> 1.70.0, oxfmt0.52.0 -> 0.55.0, vitest4.1.8 -> 4.1.9, and the oxc toolchain0.133.0 -> 0.136.0(#1749, #1767, #1812, #1834, #1855), by @voidzero-guard[bot]Fixes & Enhancements
openssl0.10.76 -> 0.10.80(openssl-sys0.9.112 -> 0.9.116), fixing five high-severity rust-openssl issues (buffer overflows in key derivation, AES key wrap, and digest finalization; an unchecked PSK/cookie trampoline length leaking adjacent memory; and OCSP-responder undefined behavior: GHSA-pqf5-4pqq-29f5, GHSA-8c75-8mhr-p7r9, GHSA-ghm9-cr32-g9qj, GHSA-hppc-g8h3-xhp3, GHSA-xp3w-r5p5-63rr), and drop the unmaintained, unsoundlibyml(GHSA-gfxp-f68g-8x78, high) by removing deadserde_ymlcode (#1742), by @fengmk2mermaid11.13.0 -> 11.15.0to fix improperclassDefsanitization in state diagrams that allowed HTML injection (CVE-2026-41149 / GHSA-ghcm-xqfw-q4vr, medium severity;<script>tags are stripped so it does not reach XSS) (#1745), by @renovate[bot]vp check --fix/vp staged: create/migrate now wrap inline Viteplugins: [...]arrays withlazyPlugins(...)so plugin factories aren't eagerly executed (and don't hang on open handles) during lint/format/check config loading (#1752), by @jong-kyungvp migrate: complete pending migration work for projects that already havevite-plusinstalled (scripts, imports, tsconfig types, ESLint/Prettier, legacy hooks, package-manager settings) instead of treatingvite-plusas migration-complete; fully migrated projects stay idempotent (#1821), by @jong-kyungvp create/vp migrate: detect shorthandfmt,/lint,config keys so a duplicate inline block is no longer injected (#1843), by @fengmk2VP_COMMANDsolazyPlugins()skips framework plugins during LSP config reads, preventing a stray.svelte-kit(and similar) directory at the monorepo root (#1764), by @jong-kyungvp lint/vp run -r linton Windows: keep the absolutetsgolintpath for workspace lint runs instead of downgrading it to a wrong cwd-relative path (#1758), by @semimikohtsgolintpath so type-aware lint resolves it (#1811), by @jong-kyungvp install -g: use a unique backup directory and treat stale-backup cleanup as best-effort so a locked Windows binary no longer fails an otherwise successful reinstall (#1753), by @fengmk2vp install -g: remove stale managed binary shims when a reinstalled package drops a bin from itspackage.json#bin(#1765), by @liangmiQwQvp create --git: surface git's actual stdout/stderr when the initial commit fails instead of always blaminguser.name/user.email(#1819), by @fengmk2vp create vite:generator: reject--git/--no-git, since adding a generator to an existing monorepo does not initialize git (#1788), by @jong-kyungfind_system_toolagainst a self-exec loop (skip the running executable's own bin directory) and fix twovite_global_clitests that could hang (#1820), by @fengmk2runoptions (#1797), show--fail-if-no-matchinexechelp (#1798), add theimplodedocumentation link (#1796), and handle nested-command typo help (#1803), by @jong-kyungDocs
vp createopt-out options (#1790), by @jong-kyungvp upgradeoptions (#1847), by @jong-kyungRefactor
vp installare already covered by the help system and added unnecessary complexity (#1799), by @cpojerChore
vite_globdependency from vite-plus (#1763), by @wan9chisync-remotefrom churningpnpm-workspace.yaml(dedupeminimumReleaseAgeExclude, preserve comments) (#1787), by @fengmk2just testrunnable (#1755), by @situ2001just lintandjust testas the single source of truth (#1809), pincargo-zigbuildto a git rev to fix the aarch64-musl link failure (#1815), and keep upgrade-deps green when rolldown bumps oxc (#1833), by @fengmk2oxc-project/setup-nodeto v1.3.1 (#1792), by @BoshenBundled Versions
8.0.16f94df871.1.1d7f919c0.22.34.1.91.70.00.23.00.55.0Upgrading from 0.1.24 to 0.2.0
This release has two breaking changes. For most projects the upgrade is
vp upgrade, bump the project'svite-plus, thenvp migrate.1. Update the CLI
2. Node.js 20 is no longer supported
The minimum supported Node.js version is now
^22.18.0 || >=24.11.0(Node 20 reached end-of-life). If you are still on Node 20:node --version(orvp env doctor)vp env pin 22.18.0(or a newer LTS), or update your.node-version/devEngines.runtimevp exec/vp run/vp dlxnow refuse to run against a project that resolves Node < 22.18.0.3. Vitest is now upstream (the wrapper is gone)
@voidzero-dev/vite-plus-testhas been removed; Vite+ consumes upstreamvitestdirectly. Bumpvite-plusfirst, then migrate:vp update --latestre-resolvesvite-plusto the newest release regardless of the old semver range, so the lockfile cannot pin you back to 0.1.24. The project's localvite-plusis then 0.2.0, and since the globalvpdelegatesmigrateto the project's local install,vp migrateruns the new migration.import { vi, ... } from 'vite-plus/test'code is unchanged.vp migraterewrites any leftovervitest/@vitest/*imports and normalizes stalevitest: npm:@​voidzero-dev/vite-plus-test@*aliases.vitestor@vitest/*yourself; they arrive transitively throughvite-plus.New Contributors
Welcome to our new contributor @situ2001! 🎉
Full Changelog: voidzero-dev/vite-plus@v0.1.24...v0.2.0
Published Packages
@voidzero-dev/vite-plus-core@0.2.0vite-plus@0.2.0Installation
macOS/Linux:
curl -fsSL https://vite.plus | bashWindows:
Or download and run
vp-setup.exefrom the assets below.View the full commit:
6f97f09Configuration
📅 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.