Skip to content

chore(deps): update vite-plus monorepo to v0.3.3 - #200

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vite-plus-monorepo
Open

chore(deps): update vite-plus monorepo to v0.3.3#200
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vite-plus-monorepo

Conversation

@renovate

@renovate renovate Bot commented Sep 5, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
vite (source) 0.2.8 → 0.3.3 age confidence
vite-plus (source) 0.2.8 → 0.3.3 age confidence

Release Notes

voidzero-dev/vite-plus (vite)

v0.3.3: vite-plus v0.3.3: Homebrew setup and workspace dependency fixes

Compare Source

This release fixes Homebrew setup, Windows installation, and workspace dependency commands. It also updates Rolldown, Oxlint, and Oxfmt.

Fixes & Enhancements
  • Homebrew installations complete setup once, retain their bundled CLI, and direct upgrades to brew upgrade vite-plus (#​2729), by @​fengmk2.
  • Windows installations decode remote legacy PowerShell scripts correctly (#​2701), by @​james-elicx.
  • vp migrate removes the unsupported React Refresh allowCompoundComponents option and warns about possible lint errors (#​2702), by @​fengmk2.
  • New monorepo packages use the root lint configuration without a conflicting nested configuration (#​2667), by @​semimikoh.
  • Yarn Classic rejects filtered additions and removals instead of changing unintended dependencies (#​2705), by @​jong-kyung.
  • Yarn Berry rejects unsupported filtered updates and respects filters during recursive removal (#​2709, #​2712), by @​jong-kyung.
  • Yarn and Bun warn when a command does not support --workspace-root. Yarn Classic accepts root additions through vp add and vp install <packages> (#​2713), by @​jong-kyung.
  • vp dedupe warns about unsupported check options (#​2717), by @​jong-kyung.
  • Rust command output respects NO_COLOR (#​2716), by @​liangmiQwQ.
  • Windows commands find lowercase shims in directories with case-sensitive file names (#​2727), by @​fengmk2.
Dependency Updates
Docs
Chore
Bundled Versions
Tool Version Source
vite 8.3.0 434e8e9
rolldown 1.2.9 5b4746e
tsdown 0.23.0 npm
vitest 4.1.11 npm
oxlint 1.83.0 npm
oxlint-tsgolint 7.0.2001 npm
oxfmt 0.68.0 npm
Upgrade
vp upgrade
New Contributors

@​james-elicx

Full Changelog: voidzero-dev/vite-plus@v0.3.2...v0.3.3

Published Packages
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.3.3 vp build

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

v0.3.2: vite-plus v0.3.2: independent package-manager versions and Oxlint plugin APIs

Compare Source

vp env use now sets each package manager's version independently. This release also adds Oxlint plugin APIs and fixes migration, installation, and template extraction.

Breaking Changes
Package-manager overrides

Direct package-manager commands no longer use VP_PACKAGE_MANAGER. Use the matching version variable in shell profiles, CI jobs, and Dockerfiles:

Previous override for a direct command New override
VP_PACKAGE_MANAGER=npm@<version> VP_NPM_VERSION=<version>
VP_PACKAGE_MANAGER=pnpm@<version> VP_PNPM_VERSION=<version>
VP_PACKAGE_MANAGER=yarn@<version> VP_YARN_VERSION=<version>
VP_PACKAGE_MANAGER=bun@<version> VP_BUN_VERSION=<version>

VP_PACKAGE_MANAGER still selects the manager and version for vp install and related commands. vp env use pnpm@10 now changes only the direct pnpm commands. To override vp install, set VP_PACKAGE_MANAGER explicitly.

The old .session-package-manager file is no longer read or migrated. Run vp env use again to create the new session files. Projects that use only project pins or global defaults need no changes. See the environment guide (#​2658, #​2659), by @​liangmiQwQ.

Installer preferences

VP_NODE_MANAGER now controls only Node.js. Existing installations retain saved preferences during upgrades, so vp upgrade needs no configuration changes. For scripted installations, set VP_PM_MANAGER to apply the same choice to package managers:

Previous combined setting New combined setting
VP_NODE_MANAGER=no VP_NODE_MANAGER=no VP_PM_MANAGER=no
VP_NODE_MANAGER=yes VP_NODE_MANAGER=yes VP_PM_MANAGER=yes

Update installer commands in CI jobs and Dockerfiles. Use VP_NPM_MANAGER, VP_PNPM_MANAGER, VP_YARN_MANAGER, or VP_BUN_MANAGER for individual preferences. The interactive prompt retains its combined choice. See the installer variables guide (#​2681), by @​liangmiQwQ.

Vite DevTools

Projects that install @vitejs/devtools must update its dependency range from ^0.4.0 || ^0.5.0 to ^0.7.1. Projects without this optional dependency need no changes. This requirement comes with the Vite upgrade listed below.

Highlights
  • Installers and vp upgrade share setup behavior across platforms, which simplifies maintenance. The installers retain support for older releases (#​2611), by @​liangmiQwQ.
  • Custom Oxlint rules can import their APIs from vite-plus/lint/plugins and vite-plus/lint/plugins-dev. vp migrate updates supported existing imports (#​2328), by @​fengmk2.
  • vp install and vp add now honor --ignore-scripts for named packages and managed global installations (#​2682), by @​jong-kyung.
Features
Fixes & Enhancements
  • vp create rejects malformed registry versions that could place organization template files outside the cache directory (#​2665), by @​fengmk2.
  • vp env pin updates an active local .nvmrc and preserves its comments. Use --target nvmrc to select this file explicitly (#​2676), by @​ywenhao.
  • vp migrate reports unsupported ESLint rules that it skips, so users can review the missing checks (#​2689), by @​yusuke99.
  • vp migrate imports leftover tsdown configuration when a project already uses Vite+ (#​2646), by @​TheAlexLichter.
  • vp migrate accepts single-line JSON formatter configuration with a final newline (#​2643), by @​TheAlexLichter.
  • vp migrate avoids a redundant playwright dependency when the project already declares @playwright/test (#​2637), by @​yusuke99.
  • Newly scaffolded local generators honor --no-interactive and report missing arguments without prompts. Existing generators need the updated entrypoint (#​2677), by @​SaKaNa-Y.
  • vp upgrade installs its dependencies correctly when the installation directory is inside a pnpm workspace (#​2644), by @​fengmk2.
  • Nested package-manager commands retain the selected Node runtime and package-manager versions (#​2631), by @​lyzno1.
  • Built-in tools reuse the Node executable that starts the CLI. Editor lint and format servers work when node is absent from PATH (#​2673), by @​fengmk2.
  • The npm command wrapper enables Node's compile cache before it loads the CLI, which reduces repeated startup work (#​2648), by @​pablog12.
  • Package-manager commands suppress pnpm, npm, and supported Yarn update notices. Yarn 4 daily tips are also hidden (#​2649, #​2650, #​2651), by @​fengmk2.
  • Invalid package.json errors include the affected file's path (#​2683), by @​adamaveray.
Docs
  • The README task example uses the supported env field (#​2653), by @​SaKaNa-Y.
  • Migration guidance tells pnpm users to retain the generated vite and vitest dependencies (#​2660), by @​naokihaba.
  • Lint and format guides explain root configuration and overrides for monorepos. They clarify that nested configuration is not supported (#​2668), by @​liangmiQwQ.
Chore
Bundled Versions
Tool Version Source
vite 8.3.0 434e8e9
rolldown 1.2.8 9704b56
tsdown 0.23.0 npm
vitest 4.1.11 npm
oxlint 1.82.0 npm
oxlint-tsgolint 7.0.2001 npm
oxfmt 0.67.0 npm
Upgrade
vp upgrade
New Contributors

@​yusuke99, @​pablog12, @​SaKaNa-Y, @​ywenhao, @​adamaveray

Full Changelog: voidzero-dev/vite-plus@v0.3.1...v0.3.2

Published Packages
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.3.2 vp build

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

v0.3.1: vite-plus v0.3.1: manage package-manager versions with vp env

Compare Source

vp env now manages Node.js and package-manager versions together. This release also fixes TanStack Start routing and stale Vitest aliases.

Breaking Changes
Package-manager setup

Vite+ replaces Corepack with managed npm, pnpm, yarn, and bun commands. It removes the corepack shim and legacy global package-manager installations (#​2391), by @​liangmiQwQ.

Replace Corepack setup commands in shell profiles, CI jobs, and Dockerfiles:

Previous setup Replacement
corepack enable vp env setup
vp install -g pnpm@<version> vp env default pnpm@<version>
vp install -g yarn@<version> vp env default yarn@<version>
vp install -g bun@<version> vp env default bun@<version>
vp install -g corepack Use the managed package-manager commands directly

Use vp env pin <manager>@<version> to set a project version.

vp env command scope and JSON output

Unscoped vp env commands now operate on Node.js and package managers. Package managers support independent defaults, project pins, session overrides, and installation commands (#​2398), by @​liangmiQwQ.

Add node to limit an operation to Node.js, for example, vp env off node or vp env unpin node. Bare versions, such as vp env default 22.19.0, still select Node.js.

Update scripts that read JSON output:

Command New output structure
vp env current --json node and package_manager objects
vp env list --json, vp env list-remote --json node and package_managers groups

See the environment guide.

vp pack migration to [email protected]

vp pack now uses [email protected], which removes deprecated options and changes defaults (#​2614), by @​fengmk2.

  1. Run vp migrate to update supported static configurations and package scripts, including projects that already use Vite+.
  2. Check migration warnings in vite.config.*, tsdown.config.*, and package.json.
  3. Update dynamic configurations manually. Arrays built with .map() require manual changes, even when migration reports no warning.
  4. Run vp pack to check the result.
Previous option Replacement
bundle: false unbundle: true
outExtension outExtensions
publicDir / --public-dir copy / --copy
removeNodeProtocol: true nodeProtocol: 'strip'
injectStyle css.inject
inlineOnly / deps.onlyAllowBundle deps.onlyBundle
noExternal deps.alwaysBundle
skipNodeModulesBundle: true / deps.skipNodeModulesBundle: true deps.neverBundle: true
dts.tsgo: true / dts.oxc: true dts.generator: 'tsgo' / dts.generator: 'oxc'

Migration preserves the previous defaults for dependency resolution and ATTW.

tsdown no longer supports Node.js 25. Use Node.js ^22.18.0, ^24.11.0, or >=26.0.0. The programmatic build() API now returns { bundles, watch }.

See the complete migration guide for declaration and TypeScript module-resolution changes.

CLI argument validation

vp staged, vp config, vp hooks, vp migrate, and vp create now reject unsupported options and extra positional arguments (#​2523), by @​fengmk2.

Remove unsupported arguments from scripts. For example, replace vp config --hooks-only with vp config --no-agent.

Highlights
  • Fix TanStack Start HTTP 404 responses caused by separate Vite runtime copies (#​2617), by @​fengmk2.
  • Reduce the Windows vp-shim.exe size from 214 KiB to 14 KiB (#​2466), by @​fengmk2.
  • Add vp check --quiet to hide lint warning diagnostics while retaining errors and summary counts (#​2593), by @​RSS1102.
Features
  • Add vp sync-versions --json so automation can request dependency alignment plans from manifest snapshots without changing project files (#​2600), by @​afonsojramos.
  • Make vp create --git suggest an initial commit command after Git initialization (#​2581), by @​fengmk2.
  • Make vp migrate replace frozen voidzero-dev/setup-vp@v1 workflow references with the supported version pin (#​2540), by @​fengmk2.
  • Upgrade rolldown from 1.2.5 to 1.2.7, tsdown from 0.22.14 to 0.23.0, and Oxc from 0.146.0 to 0.148.0. Upgrade oxlint from 1.79.0 to 1.81.0 and oxfmt from 0.64.0 to 0.66.0. These versions can flag code that passed before. Run vp fmt after upgrading if CI runs vp check (#​2580, #​2613), by @​voidzero-guard[bot].
Fixes & Enhancements
  • Resolve package-manager versions without rewriting package.json. Use vp env pin or vp env unpin to change project declarations explicitly (#​2399), by @​liangmiQwQ.
  • Let vp migrate repair stale vitest aliases that previously prevented the CLI from starting (#​2605), by @​fengmk2.
  • Keep Vite DevTools within the version ranges supported by the bundled Vite (#​2559), by @​fengmk2.
  • Keep automatic Vitest upgrades on the supported 4.x major (#​2612), by @​fengmk2.
  • Remove a deprecated tsdown option from the prompts package build (#​2597), by @​jong-kyung.
Refactor
Docs
Chore
Bundled Versions
Tool Version Source
vite 8.2.2 de1111a
rolldown 1.2.7 26b4c6e
tsdown 0.23.0 npm
vitest 4.1.11 npm
oxlint 1.81.0 npm
oxlint-tsgolint 7.0.2001 npm
oxfmt 0.66.0 npm
Upgrade
vp upgrade
New Contributors

@​afonsojramos, @​joschuba

Full Changelog: voidzero-dev/vite-plus@v0.3.0...v0.3.1

Published Packages
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.3.1 vp build

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

v0.3.0: vite-plus v0.3.0: XDG install layout, tsup project migration, and Bun 1.4 support

Compare Source

Fresh installs now use a split directory layout instead of a single ~/.vite-plus root. Unix follows the XDG base directory specification, and Windows uses the standard %LOCALAPPDATA% and %APPDATA% folders. Existing ~/.vite-plus installs keep their current directory layout. vp migrate also converts tsup projects, and vp now sends Bun 1.4 package-manager commands to bun directly. The published npm package shrank by about half, and the upgrade check no longer delays each command.

Breaking Changes

  • Fresh installs now use a split directory layout instead of a single root: XDG base directories on Unix, and the standard known folders on Windows. Existing ~/.vite-plus installs keep their current layout, and the installer does not move their files. VP_HOME still selects the single-root layout (#​2346), by @​forehalo

    Category Unix default Windows default Single-root (VP_HOME)
    bin ~/.local/share/vite-plus/bin %LOCALAPPDATA%\vite-plus\bin <root>/bin
    data ~/.local/share/vite-plus %LOCALAPPDATA%\vite-plus\data <root>
    cache ~/.cache/vite-plus %LOCALAPPDATA%\vite-plus\cache <root>/cache
    config ~/.config/vite-plus %APPDATA%\vite-plus <root>
    state ~/.local/state/vite-plus %LOCALAPPDATA%\vite-plus\state <root>

    The installer configures your shell for the new location, and CI that installs through setup-vp keeps the single-root layout automatically. Update each hard-coded ~/.vite-plus/bin path, such as a path in a Dockerfile.

    vp upgrade leaves an existing install where it is. To move one to the split layout, remove it and install again:

    vp implode
unset VP_HOME VP_DATA_DIR VP_BIN_DIR VP_CACHE_DIR
curl -fsSL https://vite.plus | bash

    On Windows, run vp implode, then Remove-Item Env:\VP_HOME, Env:\VP_DATA_DIR, Env:\VP_BIN_DIR, Env:\VP_CACHE_DIR -ErrorAction SilentlyContinue, then irm https://vite.plus/ps1 | iex. Also delete any persistent VP_HOME or VP_*_DIR definition from your shell profile or system environment, because a fresh install still honors them and VP_HOME selects the single-root layout.

    vp implode removes every Vite+ managed Node.js runtime, global package, configuration file, and cache. Stay on your current layout if you would rather not rebuild that state. See Move an existing install to the split directory layout.

Highlights
  • vp migrate now converts tsup projects. It replaces the tsup dependency and script with vp pack. It also changes tsup.config.ts to a tsdown.config.ts that imports from vite-plus/pack (#​2434), by @​KTrain5169
  • Shell integrations now accept the global -C flag. vp -C <dir> env use changes the environment of your current shell. The -C<dir> and -C=<dir> forms also work. In zsh, Fish, Nushell, and PowerShell, vpr completion keeps the working directory when it changes the command to vp run (#​2508), by @​simulacre7
  • The published vite-plus npm package shrank from 1.05 MB to 516 kB, a 51% reduction. It now includes only Markdown files from the documentation workspace. It no longer includes VitePress tooling, images, or deployment files (#​2480), by @​liangmiQwQ
Features
  • With Bun 1.4 or later, Vite+ forwards these commands and flags to bun. Earlier Bun versions keep their fallback or unsupported behavior and report the required Bun version (#​2513), by @​jong-kyung
    • vp dedupe runs bun dedupe, including --check
    • vp pm prune runs bun prune
    • vp pm audit --fix runs bun audit fix
    • vp add, vp remove, and vp update send --filter to bun
    • vp add --save-catalog sends --catalog to bun
  • The upgrade check no longer delays fast commands. It runs in a separate process. It reports an available update during a later command, and commands no longer wait for the registry (#​2380), by @​liangmiQwQ
  • Upgrade the bundled toolchain (#​2443, #​2500, #​2504, #​2519, #​2532), by @​voidzero-guard[bot]:
    • vite: 8.2.1 to 8.2.2
    • rolldown: 1.2.3 to 1.2.5
    • vitest: 4.1.10 to 4.1.11
    • oxlint: 1.77.0 to 1.79.0
    • oxfmt: 0.62.0 to 0.64.0
    • Oxc packages and crates: 0.143.0 to 0.146.0
    • Vite+ now accepts @vitejs/devtools 0.5.x. The optional peer range is ^0.4.0 || ^0.5.0. This repository uses 0.5.2.
    • oxfmt and oxlint can report new issues after the upgrade. Run vp check locally. Use vp fmt to fix formatting changes.
  • vp toolchain draws its tree with Unicode glyphs. It no longer uses ASCII connectors (#​2442), by @​liangmiQwQ
Fixes & Enhancements
  • At a workspace root, bare app commands now use defaultPackage or detected root configuration before they select a member package. A workspace without member packages runs the command in the root (#​2530, #​2533), by @​fengmk2
  • vp up no longer changes "vite": "catalog:" to a version alias under pnpm. Catalog references now stay unchanged during an update. Run vp migrate once to correct an existing project (#​2425), by @​fengmk2
  • If the server accepts range requests, an interrupted runtime download continues from the bytes on disk. It does not start again (#​2452), by @​tarikermis
  • The local CLI shows the install instructions when you run a global-only command such as env, upgrade, or implode (#​2522), by @​jong-kyung
  • vp up -g asks npm for globally installed package versions. A project-level setting no longer makes the lookup fail and hide an available update (#​2438), by @​jong-kyung
  • When hooks are disabled through HUSKY=0, VP_GIT_HOOKS=0, or VITE_GIT_HOOKS=0, vp config skips the Git lookup. This lets vp config run in a container without Git (#​2458), by @​tarikermis
  • vp create vite:monorepo now asks once about Git and runs git init once (#​2417), by @​jong-kyung
  • vp create does not ask about pre-commit hooks when you choose not to initialize Git (#​2477), by @​liangmiQwQ
  • vp pack --no-config does not read the Vite config. A local vite.config.* file, its pack options, and its hooks no longer run (#​2486), by @​jong-kyung
  • vp pack --help shows the supported --no-config options (#​2487), by @​jong-kyung
  • vp staged --no-concurrent works again. --concurrent accepts true, false, or a number greater than 0. It rejects other values. Vite+ also rejects --no-cwd, --no-diff, and --no-diff-filter (#​2501), by @​RSS1102
  • vp reads about 450 kB less JavaScript at start. It loads the --init and --migrate helpers only when a command needs them (#​2490), by @​jong-kyung
  • The standalone vp binary is smaller. Vite+ no longer copies the package-manager command tree, and it disables unused tar and dialoguer features (#​2507), by @​liangmiQwQ
  • A generated Fish environment file escapes the special characters in a path (#​2492), by @​fengmk2
  • A generated POSIX shell environment file escapes the special characters in a path. It also removes each duplicate Vite+ bin entry (#​2494), by @​fengmk2
  • The generated cmd.exe wrapper preserves the exit status from vp env use. It does not apply output after a failed command (#​2496), by @​fengmk2
  • vp exec resolves a relative PATH entry such as ./node_modules/.bin against the working directory of the command (#​2350), by @​RSS1102
  • Older GitLab setup-vp templates continue to work. The installer selects the legacy layout for them. A template can select the new layout with VP_VPDIRS_AWARE=1 (#​2520), by @​fengmk2
  • The Windows installer checks the directory variables and the requested version before it downloads a payload. It also repairs a broken current junction (#​2505), by @​fengmk2
  • install.sh does not show shell configuration warnings when CI=true (#​2511), by @​fengmk2
  • On Windows, vp implode can remove Vite+ roots that contain long or locked paths. A native helper does this work, and it retries cleanup and writes an error log if cleanup fails (#​2510), by @​fengmk2
  • A Windows trampoline sidecar must have a vite-plus-shim-v1 header. The trampoline rejects one without that header instead of guessing the install layout (#​2526), by @​fengmk2
Docs
Chore
Bundled Versions
Tool Version Source
vite 8.2.2 de1111a
rolldown 1.2.5 84c904b
tsdown 0.22.14 npm
vitest 4.1.11 npm
oxlint 1.79.0 npm
oxlint-tsgolint 7.0.2001 npm
oxfmt 0.64.0 npm
Upgrade
vp upgrade
New Contributors

@​simulacre7

Full Changelog: voidzero-dev/vite-plus@v0.2.9...v0.3.0

Published Packages
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.3.0 vp build

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

v0.2.9: vite-plus v0.2.9: add vp toolchain and vp hooks, and fix vp run inside Codex and Claude Code sandboxes

Compare Source

vp toolchain prints the tools, versions, and bundling relationships in the active release. vp hooks manages the Vite+ dispatcher for Git hooks, and removes the manual setup steps. vp run no longer fails in the default Codex CLI and Claude Code sandboxes. Those sandboxes deny Unix sockets and shared memory, which task IPC and file-access tracking used. The rest of the release makes the install path more reliable. It fixes npm 12 blocked install scripts, Yarn 2+ integrity pins, and baseline Bun builds for older CPUs. It also fixes downloads that stopped on slow connections.

Highlights
  • New vp toolchain command. It prints the tools, versions, and bundling relationships in the active Vite+ release as a tree. The tree shows vite-plus, core, vite, rolldown, oxc, oxc-resolver, and the compiled Vite Task with its build time and revision. Give a tool name to select part of the tree. Use --json for machine-readable output. Use --global for the global release (#​2111), by @​fengmk2
  • New vp hooks command. It manages the Vite+ dispatcher for Git hooks. enable installs or refreshes the dispatcher and sets core.hooksPath. disable removes the dispatcher and keeps that preference, so prepare and vp config do not install it again. status shows the current state. Use --hooks-dir to set a custom directory. Vite+ keeps that directory for later commands. Vite+ does not change project-owned hooks, staged config, or package.json lifecycle scripts (#​2341), by @​dennybiasiolli
  • vp run now works in the default Codex CLI and Claude Code sandboxes. Before this release, a cached task failed with `

❗ Important

✂ PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

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

🚦 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 these updates again.

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

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

@renovate renovate Bot added the deps label Sep 5, 2026
@pkg-pr-new

pkg-pr-new Bot commented Sep 5, 2026 •
edited
Loading

Copy link
Copy Markdown
@intlify/format-napi

npm i https://pkg.pr.new/intlify/intlify/@intlify/format-napi@200

@intlify/format-wasm

npm i https://pkg.pr.new/intlify/intlify/@intlify/format-wasm@200

@intlify/ox-mf2-napi

npm i https://pkg.pr.new/intlify/intlify/@intlify/ox-mf2-napi@200

@intlify/ox-mf2-wasm

npm i https://pkg.pr.new/intlify/intlify/@intlify/ox-mf2-wasm@200

@intlify/format-napi-darwin-arm64

npm i https://pkg.pr.new/intlify/intlify/@intlify/format-napi-darwin-arm64@200

@intlify/format-napi-darwin-x64

npm i https://pkg.pr.new/intlify/intlify/@intlify/format-napi-darwin-x64@200

@intlify/format-napi-linux-arm64-gnu

npm i https://pkg.pr.new/intlify/intlify/@intlify/format-napi-linux-arm64-gnu@200

@intlify/format-napi-linux-x64-gnu

npm i https://pkg.pr.new/intlify/intlify/@intlify/format-napi-linux-x64-gnu@200

@intlify/format-napi-linux-x64-musl

npm i https://pkg.pr.new/intlify/intlify/@intlify/format-napi-linux-x64-musl@200

@intlify/format-napi-win32-x64-msvc

npm i https://pkg.pr.new/intlify/intlify/@intlify/format-napi-win32-x64-msvc@200

@intlify/ox-mf2-napi-darwin-arm64

npm i https://pkg.pr.new/intlify/intlify/@intlify/ox-mf2-napi-darwin-arm64@200

@intlify/ox-mf2-napi-darwin-x64

npm i https://pkg.pr.new/intlify/intlify/@intlify/ox-mf2-napi-darwin-x64@200

@intlify/ox-mf2-napi-linux-arm64-gnu

npm i https://pkg.pr.new/intlify/intlify/@intlify/ox-mf2-napi-linux-arm64-gnu@200

@intlify/ox-mf2-napi-linux-x64-gnu

npm i https://pkg.pr.new/intlify/intlify/@intlify/ox-mf2-napi-linux-x64-gnu@200

@intlify/ox-mf2-napi-linux-x64-musl

npm i https://pkg.pr.new/intlify/intlify/@intlify/ox-mf2-napi-linux-x64-musl@200

@intlify/ox-mf2-napi-win32-x64-msvc

npm i https://pkg.pr.new/intlify/intlify/@intlify/ox-mf2-napi-win32-x64-msvc@200

commit: 721adf4

@renovate
renovate Bot force-pushed the renovate/vite-plus-monorepo branch 6 times, most recently from 2c950aa to af7e3a3 Compare September 10, 2026 12:23
@coderabbitai

coderabbitai Bot commented Sep 10, 2026 •
edited
Loading

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 8aa8c796-fe2d-419f-bb1d-6ca46475e0c3

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@renovate
renovate Bot force-pushed the renovate/vite-plus-monorepo branch from af7e3a3 to 5c3fb20 Compare September 17, 2026 16:29
@renovate renovate Bot changed the title chore(deps): update vite-plus monorepo to v0.3.0 chore(deps): update vite-plus monorepo to v0.3.1 Sep 17, 2026
@renovate
renovate Bot force-pushed the renovate/vite-plus-monorepo branch 17 times, most recently from 627caca to 297934c Compare September 21, 2026 21:11
@renovate renovate Bot changed the title chore(deps): update vite-plus monorepo to v0.3.1 chore(deps): update vite-plus monorepo to v0.3.2 Sep 21, 2026
@renovate
renovate Bot force-pushed the renovate/vite-plus-monorepo branch from 297934c to 647b513 Compare September 23, 2026 04:46
@renovate
renovate Bot force-pushed the renovate/vite-plus-monorepo branch 6 times, most recently from 68be4ef to 2f391e0 Compare September 25, 2026 05:11
@renovate renovate Bot changed the title chore(deps): update vite-plus monorepo to v0.3.2 chore(deps): update vite-plus monorepo to v0.3.3 Sep 25, 2026
@renovate
renovate Bot force-pushed the renovate/vite-plus-monorepo branch 5 times, most recently from 7e70abc to 4a125a6 Compare October 2, 2026 16:59
@renovate
renovate Bot force-pushed the renovate/vite-plus-monorepo branch 5 times, most recently from 155a23c to c999004 Compare October 6, 2026 17:58
@renovate
renovate Bot force-pushed the renovate/vite-plus-monorepo branch from c999004 to 721adf4 Compare October 8, 2026 04:48

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

deps

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants