chore(deps): update dependency vite-plus to v0.2.2 by renovate[bot] · Pull Request #10084 · rolldown/rolldown

renovate · 2026-07-02T10:25:56Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
vite-plus (source)	`0.2.1` → `0.2.2`

Release Notes

voidzero-dev/vite-plus (vite-plus)

`v0.2.2`: vite-plus v0.2.2: Vite+ Beta

Compare 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-aware vp build caching, and PGP-verified managed Node.js downloads.

Highlights

vp migrate upgrades existing Vite+ projects across versions: previous release notes told users not to run vp migrate for upgrades. It now runs from the global CLI when the local one is older, re-pins vite-plus and the vite -> @voidzero-dev/vite-plus-core alias across dependencies, overrides/resolutions, and catalogs in every workspace package, aligns vitest / @vitest/* by actual usage, and defaults to a version-only upgrade (pass --full to also run the first-time setup bucket: hooks, editor, agent files, lint migration) (#1891), by @fengmk2
Official Vite+ Docker toolchain image: ghcr.io/voidzero-dev/vite-plus bundles vp plus a native build toolchain on debian:bookworm-slim (amd64/arm64, non-root). Since vp provisions 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 @fengmk2
Zero-config vp build caching via runner-aware Vite: Vite reports its inputs, outputs, and tracked env reads to the vp runner over the new @voidzero-dev/vite-task-client IPC (vite#22453), so vp build caches correctly with no hand-written cache config: outputs are tracked and restored automatically, and a changed VITE_* env var invalidates the cache and is named in the cache-miss message (#1774), by @wan9chi
PGP-verified Node.js downloads: installing a managed Node.js now verifies the release's clearsigned SHASUMS256.txt.asc against the vendored Node.js release keyring (pure Rust, no gpg required) 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 @fengmk2

Features

vp check: a check block in vite.config.ts (check.fmt / check.lint) can make plain vp check skip formatting or linting by default, mirroring --no-fmt / --no-lint; standalone vp fmt / vp lint and git hooks are unaffected, and a note: line keeps the config-based skip discoverable (#1981), by @fengmk2
vp env list-remote: highlight installed versions (color, or a * prefix when piped) and label the project-resolved current and global default versions; --json gains installed / current / default fields (#1907), by @semimikoh
vpr ships as a vite-plus package bin, so the vp run shorthand works on clean installs without global PATH shims (Vercel build image, generic CI runners) (#1988), by @kvnwolf
Vite Task: dependsOn can select tasks from dependency packages, e.g. dependsOn: [{ "task": "build", "from": "dependencies" }] (vite-task#479), by @wan9chi
Vite Task: a task's env / untrackedEnv glob 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 @wan9chi
Upgrade upstream dependencies: vite 8.0.16 -> 8.1.2, rolldown 1.1.1 -> 1.1.4, oxlint 1.70.0 -> 1.72.0, oxfmt 0.55.0 -> 0.57.0, oxlint-tsgolint 0.23.0 -> 0.24.0, and the oxc toolchain 0.136.0 -> 0.138.0 (#1924, #1989, #2000, #2009), by @voidzero-guard[bot]

Fixes & Enhancements

Windows: vp run no longer hangs CI when a node_modules/.bin .cmd shim is routed through PowerShell; the npm/pnpm/yarn .ps1 wrappers 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 @fengmk2
Vite Task: the task cache is stored in a per-schema-version directory (e.g. node_modules/.vite/task-cache/v13/), so switching between branches that pin different Vite+ versions no longer fails with Unrecognized database version (vite-task#433), by @fengmk2
Vite Task: env values in cache fingerprints are stored only as SHA-256 digests and env cache-miss details report names without values (vite-task#455); prefix env assignments like PATH=... command now affect executable lookup during planning (vite-task#440); package.json / pnpm-workspace.yaml files with a UTF-8 BOM parse correctly (vite-task#424), by @wan9chi
vp upgrade: run the pinned pnpm with a managed Node.js LTS directly instead of re-entering vp 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 @liangmiQwQ
Global package installs: each install writes to an immutable packages/<name>#<uuid> prefix that is activated via metadata after npm succeeds, so an interrupted reinstall can no longer leave the active package unavailable (#1906), and stale interrupted-install directories are swept with file-lock protection for concurrent installs (#1945), by @liangmiQwQ
lazyPlugins(): skip plugin factories only while config metadata is being resolved instead of keying off VP_COMMAND, so builds spawned under vp run / vp exec keep the user's plugins and vp format no longer loads them (#1939), by @fengmk2
vp migrate (pnpm): add a direct vite devDep aliased to the core override wherever vite-plus is depended on, so vitest's vite peer binds to @voidzero-dev/vite-plus-core instead of pulling in a second upstream vite that broke the vp test cache (#1933), by @fengmk2
vp pack: bundle @tsdown/exe and @tsdown/css into core so --exe and CSS bundling work without a resolvable top-level tsdown; the native lightningcss becomes an optional peer loaded lazily with an actionable error (#1919), by @fengmk2
vp env: invalidate stale shim resolve cache entries when the project's Node.js version source changes (#1951), by @jong-kyung
Node shim: when the project declares npm via packageManager / devEngines.packageManager, child processes spawned from node resolve the managed npm instead of the Node-bundled one (#1938); vp env which reports bins linked by an intercepted npm install -g (e.g. tsc) instead of "not found" (#1968); bins with uppercase names (e.g. vitePlus) dispatch correctly (#1963), by @liangmiQwQ
vp-setup: pass the configured npm registry to the inner pnpm install so setup works behind custom registries (#1795), by @daflyinbed
Native binding: declare the platform packages' true ABI floor engines.node >=20.0.0 so engine-strict package managers (pnpm) no longer skip the optional native dependency and fail with Cannot find native binding when a consumer's Node floor lands in a product-policy gap (#1993), by @fengmk2
vp create: run git init without creating an initial commit, so commitlint-configured templates no longer reject the hardcoded message and template placeholders are not baked into history (#2008), by @forehalo
vp staged --debug: inline the bundled lint-staged version so debug logging no longer crashes reading a package.json that does not exist in the bundle (#1925), by @rokuosan
Installer: retry downloads truncated mid-body in HttpClient::get_bytes (the platform-tarball path for vp upgrade and the standalone installer) (#1940), and clean up the temp dir when a package-manager install fails instead of leaking .tmpXXXX directories (#1949), by @shulaoda
Windows/msys: normalize backslashes in the env.fish fallback path (#1954), by @Aalivexy
install.ps1: detect the missing VC++ runtime (0xC0000135) and print VC++ Redistributable guidance instead of a generic failure; interactive irm | iex installs keep the shell open (#1962), by @cheezone
vp migrate: preserve comments, key order, and trailing commas in existing .vscode / .zed JSONC configs by patching the original text instead of re-serializing it (#1956), by @fengmk2
Migration: link the git hook warning to the migration guide (#1902), by @naokihaba
vp info / vp view: use package-manager-native commands (pnpm view, bun info, yarn npm info) instead of routing every lookup through npm view (#1895), by @jong-kyung
Correct overused ErrorConfig error types across the codebase (#1934), by @liangmiQwQ

Refactor

vite_install: centralize Yarn v1/berry branching with is_yarn_berry (#1897), by @jong-kyung

Docs

Document Vite Task automatic tracking (fs tracking and cache-reporting tools), reusing the task cache with GitHub Actions cache, and dependsOn: [{ task, from: "dependencies" }] (#1992), by @wan9chi
Rewrite the "Upgrading Vite+" guide: preview builds install through the registry bridge as ordinary 0.0.0-commit.<sha> npm versions, and vp migrate is the recommended way to upgrade a project or move it onto a preview build (#1965), by @fengmk2
Describe how to switch back to the release version from nightly (#1887), by @situ2001
Clarify Git hook tool migration (#1901), by @naokihaba
Add a global installation explanation (#1915), update the vp env help output (#1969), and add liangmiQwQ as a team member (#1911), by @liangmiQwQ
Fix package manager command examples (#1937) and the dependsOn guide link (#1883), by @jong-kyung
Remove Fathom analytics from the uninstall docs (#1946), by @mdong1909
Center the README logo and fix its size (#1878), by @hyf0

Chore

Prevent Vite beta upgrades in the upstream-deps script (#1879), stabilize flaky network-dependent tests (#1923), and bump the ecosystem-ci bun-vite-template to the oxlint jsx-a11y fix (#1898), by @fengmk2
Pin snap-test install fixtures to a published vite-plus version so release-branch CI can pass before the new version is published (#2017), by @fengmk2
Update the deprecated VITE_PLUS_ env var prefixes to VP_ in the RFCs (#1984), by @liangmiQwQ
CI: skip full CI for docs-only PRs (#1991) and for the docs deploy config (#2015), by @wan9chi
Update GitHub Actions (#1904, #1977), claude-code-action to v1.0.158 (#1979), and pnpm to v10.34.4 (#1996), by @renovate[bot]
Update oxc-project/security-action to v1.0.8 (#1918), by @fengmk2
Refresh trusted stack stats on the docs homepage (#1913, #1982), by @voidzero-guard[bot]

Bundled Versions

Tool	Version	Source
vite	`8.1.2`	`ba31193`
rolldown	`1.1.4`	`6cbd233`
tsdown	`0.22.3`	npm
vitest	`4.1.9`	npm
oxlint	`1.72.0`	npm
oxlint-tsgolint	`0.24.0`	npm
oxfmt	`0.57.0`	npm

Upgrade

vp upgrade

New to Vite+? Start with the Beta announcement, then create a project with vp create or bring an existing one over with vp migrate.

New Contributors

Welcome to our new contributors @rokuosan, @Aalivexy, @cheezone, @daflyinbed, @forehalo, @kvnwolf! 🎉

Full Changelog: voidzero-dev/vite-plus@v0.2.1...v0.2.2

Published Packages

@voidzero-dev/[email protected]
[email protected]

Installation

macOS/Linux:

curl -fsSL https://vite.plus | bash

Windows:

irm https://vite.plus/ps1 | iex

Or download and run vp-setup.exe from the assets below.

Docker:

docker run --rm -it -v "$PWD:/app" -w /app ghcr.io/voidzero-dev/vite-plus:0.2.2 vp build

Run any vp command without installing it; see the Docker guide for more.

Configuration

📅 Schedule: (in timezone Asia/Shanghai)

Branch creation
- At any time (no schedule defined)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

netlify · 2026-07-02T10:26:19Z

✅ Deploy Preview for rolldown-rs canceled.

Name	Link
🔨 Latest commit	`61b8cd0`
🔍 Latest deploy log	https://app.netlify.com/projects/rolldown-rs/deploys/6a4843e744b16400084b61a4

socket-security · 2026-07-02T10:26:40Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/vite-plus@0.2.2

View full report

socket-security · 2026-07-02T10:26:42Z

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		Obfuscated code: npm `oxfmt` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → `npm/[email protected]` → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `oxfmt` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → `npm/[email protected]` → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

renovate · 2026-07-03T23:22:49Z

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

It exposed a potential issue (#10132), so revert it to avoid blocking CI. Reverts the vite-plus `0.2.2` upgrade from #10084 (df05eba). This pins `vite-plus` and its bundled oxc toolchain back to the `0.2.1`-era versions: - `vite-plus` / `@voidzero-dev/vite-plus-*`: `0.2.2` -> `0.2.1` - `oxfmt`: `0.57.0` -> `0.55.0` - `oxlint`: `1.72.0` -> `1.70.0` - `oxlint-tsgolint`: `0.24.0` -> `0.23.0` Only the `vite-plus` dependency closure changed; no unrelated packages are touched.

…tered as executed (#10132) closes #10149 ## Problem Editing a file right after a page loads can be silently lost in full bundle mode. The dev engine decides whether a client needs an HMR update by checking the client's `executed_modules` set, but that set is reported asynchronously by the browser runtime (batched `hmr:module-registered` messages over the socket) and can lag what the client actually ran. When the edit is processed before the reports arrive, `compute_out_hmr_prerequisites` skipped the changed module for that client and produced an empty update. Vite's bundled dev ignores updates that carry no patches, and the HMR module cache had already advanced past the edit, so nothing ever re-delivers it. The page stays stale forever with no error. This is what turned main red after #10084. The vite-plus 0.2.2 bump added CPU contention on the 4-core CI runners, which stretched the report lag past the watcher debounce window, so the first edit in `playground/hmr-full-bundle-mode` started losing the race in roughly one of five jobs ([example run](https://github.com/rolldown/rolldown/actions/runs/28688065031/job/85085418310)). The three test failures in that suite are a cascade from the single lost edit. ## Fix `compute_out_hmr_prerequisites` now receives the existing `changed_modules` set. When a changed module is not registered as executed by a client, the update for that client falls back to a full reload with an explicit reason instead of being skipped. The default `RebuildStrategy::Auto` upgrades the task to a rebuild, and Vite defers the reload until `onOutput`, so the reload always lands on fresh output. The invalidate flow passes an empty `changed_modules` set and keeps the old skip. Nothing changed on disk there, so an unexecuted importer has nothing to re-run. The importer pruning inside `propagate_update` is also untouched, since that behavior is pinned by the `client-module-execution-status` fixture. Known cost: with lazy compilation, a client that never fetched the changed lazy module now reloads unnecessarily. We cannot tell it apart from a client whose loaded bundle bakes in the now stale initializer without a bundle epoch in the protocol. ## Tests A new snapshot fixture `topics/hmr/changed_module_not_executed_by_client` drives an HMR step against a client with an empty `executed_modules` set, enabled by a new `dev.unregisteredClient` test config flag. On the old code the same fixture produces an empty patch (`applyUpdates([])`) instead of the full reload, so the snapshot pins the fix. All existing HMR snapshots, the full integration suite, and the node dev server fixtures pass unchanged. ## Follow ups Two narrower windows of the same class remain and are left for separate issues. A changed module that is already registered while its accept boundary importer is not can still yield an empty patch. And when no client is registered at all, the update list is empty and Vite still ignores it, which needs a check on the Vite side when a client first registers.

@V1OL3TF0X

## [1.1.5] - 2026-07-08 ### 🚀 Features - detect top-level import-binding reads as execution-order sensitive (#10180) by @hyf0 - sourcemap_filenames: add a sourcemapFileNames option (#9271) by @V1OL3TF0X - binding: record plugin hook result kind in tracing spans (#10154) by @IWANABETHATGUY - linking: skip side-effect-free modules in per-entry reachability (#10111) by @IWANABETHATGUY - improve error message for unresolved virtual imports (#10156) by @sapphi-red - add descriptive metadata to plugin API (#10106) by @sapphi-red - add `--configLoader=native` option (#10118) by @sapphi-red ### 🐛 Bug Fixes - improve invalid annotation warnings (#10185) by @hyf0 - keep deduplicated asset filenames stable once they can be observed (#10191) by @shulaoda - sourcemap_filenames: use public option name in pattern errors (#10188) by @IWANABETHATGUY - sourcemap_filenames: hash prepared sourcemap content (#10178) by @hyf0 - tree-shake unused circular declarators exported via export list (#10166) by @IWANABETHATGUY - dev: don't panic when an HMR rebuild hits an unresolved import (#10162) by @shulaoda - propagate errors from output.globals function (#9880) by @shulaoda - dev: revert cache mutations when a partial scan fails (#10110) by @shulaoda - dev: update importer relationships of cached modules in incremental build (#10107) by @shulaoda - hmr: fall back to full reload when a changed module is not registered as executed (#10132) by @shulaoda - chunk-optimizer: follow entry facade edges in runtime placement cycle check (#10101) by @hyf0 - dev: ignore watcher events after close (#10113) by @hyf0 - emit async wrapper for TLA modules under onDemandWrapping (#10086) by @IWANABETHATGUY - gate sideEffects:false modules' side effects on body demand (#10080) by @IWANABETHATGUY - rolldown_plugin_vite_resolve: return empty object for `browser: false` mapped modules (#10082) by @sapphi-red - reset the word-boundary state on newline in Hires::Boundary sourcemaps (#10025) by @shulaoda - trim an emptied chunk's outro/intro instead of skipping past it (#10029) by @shulaoda - test each edited chunk's own start against indent exclude ranges (#10026) by @shulaoda - preserve sourcemap mappings for indented lines when a CJS module shares the chunk (#10074) by @hyf0 ### 🚜 Refactor - separate tree-shaking side effects from execution order sensitivity (#10168) by @hyf0 - type construct_vite_preload_call to take an ObjectPattern (#10135) by @shulaoda - treeshake: single-source the own-export classification shared with the lazy-barrel loader (#10098) by @IWANABETHATGUY - dev: reuse Vite's bundledDev server (#10081) by @h-a-n-a - clippy: ban std HashMap/HashSet in favour of FxHashMap/FxHashSet (#10108) by @Boshen - treeshake: make body demand a second module bit instead of a stmt multimap (#10097) by @IWANABETHATGUY - seal used_symbol_refs by construction after its last writer (#10091) by @hyf0 - treeshake: replace inclusion mutual recursion with a worklist engine (#10096) by @IWANABETHATGUY - treeshake: split include_statements.rs into focused modules (#10095) by @IWANABETHATGUY - drop redundant is_user_defined filter on partitioned entries (#10050) by @shulaoda - project the retained export interface out of used_symbol_refs (#10089) by @hyf0 - track used external symbols separately from used_symbol_refs (#10088) by @hyf0 - make module namespace inclusion an explicit linking metadata field (#10087) by @hyf0 - rename statement evaluation metadata (#10078) by @hyf0 ### 📚 Documentation - virtual modules user-facing id convention (#10155) by @sapphi-red - cli: clarify disabling boolean/object flags like codeSplitting (#10153) by @IWANABETHATGUY - chore: remove Vite+ alpha banner (#10105) by @mdong1909 - write down the used_symbol_refs contract (#10090) by @hyf0 - dev/lazy: update design and implementation (#10079) by @h-a-n-a ### ⚡ Performance - ast_scanner: stop order-sensitivity checks once a module is flagged (#10190) by @IWANABETHATGUY - return impl ExactSizeIterator from slice-backed accessors (#10133) by @Boshen - binding: box dev and watcher napi futures (#10103) by @Boshen ### 🧪 Testing - move string_wizard replace unit tests to the JS magic-string suite (#10176) by @IWANABETHATGUY - dev: assert incremental scan state matches a fresh full build after each HMR step (#10115) by @shulaoda - dev: restore runtime assertions of delete_file_not_used_anymore (#10112) by @shulaoda - dev: fix flaky dev server tests in CI (#10152) by @h-a-n-a - add regression test for #10099 (lazyBarrel drops default-import binding but keeps its property reads) (#10109) by @IWANABETHATGUY ### ⚙️ Miscellaneous Tasks - deploy website to Void via GitHub OIDC (#10192) by @Boshen - deps: update oxc to 0.139.0 (#10161) by @shulaoda - deps: update test262 submodule for tests (#10160) by @rolldown-guard[bot] - rolldown_plugin_utils: remove dead asset-url and css scaffolding (#10131) by @shulaoda - deps: revert vite-plus to v0.2.1 (#10148) by @shulaoda - deps: update github actions (#10141) by @renovate[bot] - deps: update dependency rust to v1.96.1 (#10145) by @renovate[bot] - deps: update npm packages (#10142) by @renovate[bot] - deps: update rust crates (#10143) by @renovate[bot] - deps: update napi to v3.10.3 (#10121) by @renovate[bot] - rolldown_utils: remove unused time module (#10138) by @shulaoda - remove dead CopyModulePlugin::is_active method (#10129) by @shulaoda - remove dead LazyCompilationContext::is_lazy_module method (#10128) by @shulaoda - remove dead BuildDiagnostic::downcast_ref method (#10127) by @shulaoda - deps: update dependency vite-plus to v0.2.2 (#10084) by @renovate[bot] - deps: update rust crate oxc_sourcemap to v8.1.0 (#10122) by @renovate[bot] - deps: update crate-ci/typos action to v1.48.0 (#10124) by @renovate[bot] - enable more clippy restriction lints (#10114) by @Boshen - deps: update rust dependencies (#10100) by @Boshen - deps: update oxc resolver to v11.23.0 (#10083) by @renovate[bot] ### ◀️ Revert - Revert "chore(deps): revert vite-plus to v0.2.1" (#10157) by @h-a-n-a - "fix(hmr): fall back to full reload when a changed module is not registered as executed (#10132)" (#10151) by @shulaoda ### ❤️ New Contributors * @V1OL3TF0X made their first contribution in [#9271](#9271) Co-authored-by: shulaoda <[email protected]>

renovate Bot force-pushed the renovate/vite+ branch 12 times, most recently from 5ce060b to d423b62 Compare July 3, 2026 03:33

shulaoda approved these changes Jul 3, 2026

View reviewed changes

shulaoda self-assigned this Jul 3, 2026

renovate Bot force-pushed the renovate/vite+ branch 4 times, most recently from 56e1794 to fd58107 Compare July 3, 2026 08:14

shulaoda marked this pull request as draft July 3, 2026 08:19

renovate Bot force-pushed the renovate/vite+ branch 5 times, most recently from 20e1b20 to 7da5700 Compare July 3, 2026 10:23

chore(deps): update dependency vite-plus to v0.2.2

d8e3ab2

renovate Bot force-pushed the renovate/vite+ branch from 7da5700 to d8e3ab2 Compare July 3, 2026 23:14

u

61b8cd0

shulaoda marked this pull request as ready for review July 3, 2026 23:39

shulaoda merged commit df05eba into main Jul 3, 2026
52 of 54 checks passed

shulaoda deleted the renovate/vite+ branch July 3, 2026 23:40

This was referenced Jul 4, 2026

fix(hmr): fall back to full reload when a changed module is not registered as executed #10132

Merged

chore(deps): revert vite-plus to v0.2.1 #10148

Merged

rolldown-guard Bot mentioned this pull request Jul 8, 2026

release: v1.1.5 #10194

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(deps): update dependency vite-plus to v0.2.2#10084

chore(deps): update dependency vite-plus to v0.2.2#10084
shulaoda merged 2 commits into
mainfrom
renovate/vite+

renovate Bot commented Jul 2, 2026 •

edited

Loading

Uh oh!

netlify Bot commented Jul 2, 2026 •

edited

Loading

Uh oh!

socket-security Bot commented Jul 2, 2026 •

edited

Loading

Uh oh!

socket-security Bot commented Jul 2, 2026 •

edited

Loading

Uh oh!

renovate Bot commented Jul 3, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

renovate Bot commented Jul 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

v0.2.2: vite-plus v0.2.2: Vite+ Beta

Highlights

Features

Fixes & Enhancements

Refactor

Docs

Chore

Bundled Versions

Upgrade

New Contributors

Published Packages

Installation

Configuration

Uh oh!

netlify Bot commented Jul 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for rolldown-rs canceled.

Uh oh!

socket-security Bot commented Jul 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

socket-security Bot commented Jul 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

renovate Bot commented Jul 3, 2026

Edited/Blocked Notification

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate Bot commented Jul 2, 2026 •

edited

Loading

`v0.2.2`: vite-plus v0.2.2: Vite+ Beta

netlify Bot commented Jul 2, 2026 •

edited

Loading

socket-security Bot commented Jul 2, 2026 •

edited

Loading

socket-security Bot commented Jul 2, 2026 •

edited

Loading