Repository navigation
chore(deps): update vite-plus monorepo to v1.6.0 - #52
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Remote cache stagingCommit: The source checks did not pass. No verified Cloudflare staging deployment is ready. See the workflow run. |
renovate
Bot
force-pushed
the
renovate/vite-plus-monorepo
branch
from
November 11, 2026 05:33
fb7e32b to
b1ebc77
Compare
renovate
Bot
force-pushed
the
renovate/vite-plus-monorepo
branch
from
November 11, 2026 12:54
b1ebc77 to
1b1dad2
Compare
This branch has not been deployed
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:
1.5.0→1.6.01.5.0→1.6.0Release Notes
voidzero-dev/vite-plus (vite)
v1.6.0: vite-plus v1.6.0Compare Source
Vite+ 1.6.0 caches
vp runtasks that rewrite files they read, previews runs withvp run --dry-runand JSON output, letsvp check --continue-on-errorreport every failed check, and setsVP_USER_AGENTfor the tools thatvpstarts.Features
vp runcaches tasks that read files they also write, such astsdown --exportsrewritingpackage.jsonortsc --incrementalreading and writingtsconfig.tsbuildinfo. The files a task writes, and folders that hold only those files, may be missing on the next run, as on a fresh clone, and a cache hit restores them with the task's outputs, including the symbolic links the task created (docs) (vite-task#913, vite-task#914, vite-task#915, vite-task#916, vite-task#917, vite-task#918), by @wan9chi.vp run --dry-runshows each command that a run would start and whether it would hit the cache, without running anything or writing to the cache.vp run --jsonprints every package and task in the workspace, andvp run --dry-run --jsonprints the run plan with each step's cache status, as one JSON document for scripts, CI, and coding agents.vp run -vlists every change behind a cache miss, including each changed input file, and-vvalso lists the unchanged inputs and the outputs that a hit restores (docs) (vite-task#948, vite-task#960, vite-task#961, vite-task#963, vite-task#966, vite-task#967, vite-task#968, vite-task#969), by @wan9chi.vp check --continue-on-errorruns the remaining enabled checks after a failure, so one run reports formatting, lint, and type errors together, and exits with the status of the first failed check. Without the flag,vp checkstill stops at the first failed check (#3367), by @chbaefront.vp,vpr, andvpxsetVP_USER_AGENT=vp/<version>for their child processes, so tools can detect that Vite+ started them. When the global CLI delegates to a project's local CLI, the local version is reported (docs) (#1958), by @fengmk2.VP_ENV_FORBIDDEN=1, for systems such as NixOS that provide Node.js and package managers themselves: with it set, Vite+ never downloads a Node.js or package-manager version, shims andvpxuse only the system tools onPATH, and installers andvp upgradeuse the systemnodeandpnpmfor Vite+'s own dependencies. In this release, commands that delegate to a package manager, such asvp installandvp run, fail withDisabledByEnvForbiddenwhile it is set. A follow-up change is planned to cover them and document the variable (#3233), by @myuron.oxfmt@0.76.0tooxfmt@0.78.0. Oxfmt formats Vue files with its own formatter instead of Prettier, so the output for Vue templates can change. It also fixes Tailwind class sorting in several layouts, Less escapes and%selectors, and TypeScript in Astro files.oxlint@1.91.0tooxlint@1.93.0andoxlint-tsgolint@7.0.2005tooxlint-tsgolint@7.0.2006.no-redeclaregets anignoreDeclarationMergeoption, andpromise/prefer-catchoffers a suggestion.rootinvite.config.tsfrom the directory of the config file instead of the current directory, so editor integrations in multi-root workspaces load the correct project.vp upgradewithpnpm@10.34.9(waspnpm@10.34.7).vp check, runvp check --fix --continue-on-errorafter you upgrade: it formats files, applies the available lint fixes, formats again, and reports every error that remains. For example,unicorn/prefer-type-errornow also reports athrowin anifbranch without braces, and this command rewrites it.Fixes & Enhancements
Installing global packagesinvp install -g, Vite+ hides the cursor and discards typed keys. Pressing Enter no longer leaves copies of the spinner row, and typed text no longer runs in the shell after the command ends. Ctrl+C during a spinner now ends the command with the usual signal status instead of exit code 0, and the global package spinners show the elapsed time (#3373, #3417), by @jong-kyung and @fengmk2.vp runloads a package'svite.config.*only when the run reaches one of that package's tasks. A run in one package no longer waits for the configs of other packages, a broken config in another package no longer fails it, andvp run <task>in a package that does not define the task reportsTask "<task>" not foundinstead of another package's config error (vite-task#944, vite-task#988), by @wan9chi.vp run nope#build, where no workspace package has the namenope, fails withPackage 'nope' not found in the workspaceand exits with code 1, instead of running nothing and exiting with code 0. A short name that matches several scoped packages fails as ambiguous (vite-task#984), by @wan9chi.dist, so adistfolder that appears or disappears in a folder a task lists makes the next run a cache miss. Exclusions in a task'sinput, such as"!dist/**", now also apply to the folders that the task lists. In a new monorepo fromvp create, every task hits the cache from the thirdvp run ready, because the first build creates thedistfolders (vite-task#919, vite-task#941), by @wan9chi.vp run: on Windows, files that a task deletes or moves are no longer among its inputs. Tasks that readnode_modules/.vite/task-cache, as Parcel and Gatsby do, hit the cache. A task that writes outside the workspace through.., likecp -r dist ../site, no longer fails withCache update failed(vite-task#937, vite-task#940, vite-task#980), by @wan9chi.outputglobs match as links, instead of dropping them (vite-task#885), by @jasonkuhrt.vp runchecks their cache entries in parallel, so cache hits start sooner (vite-task#982), by @wan9chi.shorbashbehave as on Linux: awhile readloop with a redirect underset -eno longer exits the script, anEXITtrap sees the exit status, so a failed task is no longer reported as successful, and$BASHis set (vite-task#939), by @lifeiscontent.vp runwrites to the system temp directory go in one folder that only the current user can write to, such as/tmp/vp_run-1000on Linux. On Linux, a different Vite+ version run by another user no longer fails (vite-task#947, vite-task#974), by @wan9chi.getEnvsquery from@voidzero-dev/vite-task-clientthat matches every name ({ prefix: '' }or*) returns nothing and no longer adds every environment variable to the cache key (vite-task#976), by @wan9chi.vp migrateno longer writes package specs that the package manager cannot resolve, such as a@vitest/*catalog:reference without a catalog entry or a top-level catalog on Bun before 1.2.21. Bun projects with an emptyworkspacesfield get catalog references, and child packages with a plainvite-plusrange get the same concrete version as the root when the project cannot use catalogs (#3397), by @jong-kyung.vp createuses the package manager version thatVP_PACKAGE_MANAGERselects for the generated settings, the installation, and its summary. Standalone pnpm projects getpackages: ['.']in an existingpnpm-workspace.yamlonly for pnpm before 10.5.0 (#3197), by @evan-lc and @fengmk2.vpsends aUser-Agentheader on all HTTP requests, so Node.js mirrors that reject requests without one, such asmirrors.aliyun.com, work (#3425), by @naokihaba.vp env pinprintsUpdatedwhen it overwrites an existing.node-versionor.nvmrcfile andCreatedwhen it writes a new one (#3377), by @CheHyeonYeong.Docs
-vvin thevp runguide (#3419, #3421), by @wan9chi.Chore
cb1ea8d, with its user-facing changes listed above, and list--dry-run,--json, and-vvinvp run --help(#3418), by @wan9chi.vp createCI job under pnpm and Bun (#3423), by @wan9chi.donecheck did not cover (#3403), by @jong-kyung.Bundled Versions
8.3.75def9361.2.18f9a49d61.0.17ff14c30.23.45.1.01.93.07.0.20060.78.0Upgrade
If
vp upgrademust download Node.js andVP_NODE_DIST_MIRRORpoints to a mirror that rejects requests without aUser-Agentheader, such asmirrors.aliyun.com, unset it or point it to another mirror for this upgrade. The installedvpdownloads Node.js and does not send the header yet.New Contributors
@alexicum, @evan-lc, @CheHyeonYeong
Full Changelog: voidzero-dev/vite-plus@v1.5.1...v1.6.0
Published Packages
@voidzero-dev/vite-plus-core@1.6.0vite-plus@1.6.0create-vite-plus@1.6.0Installation
macOS/Linux:
curl -fsSL https://vite.plus | bashHomebrew (macOS/Linux):
See the Homebrew guide to switch from the script installer or the Homebrew Core
vite-plusformula.Windows:
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:1.6.0 vp buildRun any
vpcommand without installing it; see the Docker guide for more.Create a New App
Start a project without installing the global
vp:create-vite-plusrunsvp createthrough your package manager.Run the command without arguments to pick a template interactively, and see the create guide for other package managers, templates, and options.
v1.5.1: vite-plus v1.5.1Compare Source
Vite+ 1.5.1 fixes two high-severity security issues in package-manager downloads and
vp env use, restores interactive input invp runtasks, fixesvp migrateconfig merges, and adds a reference page for each package command.Features
vite@8.3.5tovite@8.3.7. A pnpm install no longer turns every cached build into a cache miss, because Vite tells Vite Task to ignorenode_modules/.modules.yaml. It also fixes named imports from Node.js built-ins and reloads in bundled dev mode, subpath imports (#) in the dependency optimizer, SSR builds withbuild.ssr: true, and chunks shared with workers.rolldown@1.2.16torolldown@1.2.18, with module source maps that keep only the sources and names that they trace.@voidzero-dev/vite-plus-corerequirespostcss@^8.5.32, as the bundled Vite does.Fixes & Enhancements
packageManagerfield instead of the hash that the registry reports. A registry set in a project's.npmrccan no longer make Vite+ run a package manager that does not match (GHSA-5qr3-w62x-jmwx, high). Mirrors and private registries that serve the same package still pass. Each pinned version gets its own cache directory, so a project with a pinned package manager downloads it once more after the upgrade. Unpinned installs keep their current location (#3400), by @fengmk2 and @arkmarta.vp env useand other dist-tag lookups, such aspnpm@latest, accept only a valid semver version from the registry, so a registry set in a project's.npmrccan no longer put shell commands into the statements that thevp env useshell wrapper runs (GHSA-p79r-mf8q-r78h, high) (#3395), by @fengmk2 and @arkmarta.vp runstarts get a blocking stdin again when therunblock ofvite.config.tsis not statically analyzable (for example, a task command held in a constant), so interactive prompts such asvp update --interactivewait for input instead of failing withEAGAIN(#3361), by @everton-dgn.vp migratechanges only thereturnstatements of adefineConfigcallback, so functions inside the config, such as RolldowncodeSplitting.groups[].namecallbacks, keep their return values and the build no longer fails. When a callback return cannot receive the merged settings, migration keeps the standalone config files and asks for a manual merge. Pack and task cache migration also recognize configs wrapped in parentheses,as,satisfies,<T>, or!(#3325, #3372), by @jong-kyung.vp create react-routerpasses--no-git-inittocreate-react-router, so the generator's initial commit no longer stops the Vite+ setup when no Git identity is configured (#3363), by @chbaefront.env.fishcalls fish built-ins throughbuiltin, sovp env usechanges the Node.js version even when a user function has the name of a built-in such ascount(#3353), by @naokihaba.vp i<Tab>offersinstallandvp up<Tab>offersupdate. An alias stays available when no full name matches (#3337), by @nekomoyi.vp runandvprskips comment keys such as"# docs #"inpackage.jsonscripts, matches task names that contain:, and shows each task's command as its description in Zsh and Fish (#3354), by @nekomoyi.vp pm dist-tag rmworks with Yarn Berry, because Vite+ passesremovetoyarn npm tag(#3358), by @jong-kyung.Docs
Chore
@napi-rs/cli@3.10.12, let the linker reject unresolved symbols, and run Linux CI onubuntu-latestagain. Let the dependency upgrade workflow change workflow files (#3349, #3384), by @fengmk2.AGENTS.mdseparates thevite-pluspackage from the globalvpCLI and replacesCLAUDE.md, and the Node.js version RFCs describe.nvmrcsupport (#3388, #3383), by @liangmiQwQ and @hyunbinseo.import.meta.dirname, so the docs dev server no longer warns about__dirname(#3379), by @liangmiQwQ..node-versionparse tests into one table (#3355), by @Brooooooklyn.Bundled Versions
8.3.75def9361.2.18f9a49d61.0.17ff14c30.23.45.1.01.91.07.0.20050.76.0Upgrade
New Contributors
@chbaefront, @everton-dgn
Full Changelog: voidzero-dev/vite-plus@v1.5.0...v1.5.1
Published Packages
@voidzero-dev/vite-plus-core@1.5.1vite-plus@1.5.1create-vite-plus@1.5.1Installation
macOS/Linux:
curl -fsSL https://vite.plus | bashHomebrew (macOS/Linux):
See the Homebrew guide to switch from the script installer or the Homebrew Core
vite-plusformula.Windows:
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:1.5.1 vp buildRun any
vpcommand without installing it; see the Docker guide for more.Create a New App
Start a project without installing the global
vp:create-vite-plusrunsvp createthrough your package manager.Run the command without arguments to pick a template interactively, and see the create guide for other package managers, templates, and options.
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.