release: v0.2.3: config extraction, create, and vp run reliability fixes#2081
Merged
Conversation
✅ Deploy Preview for viteplus-preview canceled.
|
NAPI bakes the package.json version into binding/index.cjs version checks. The prepare_release workflow bumps package.json but does not regenerate this file, so the CI build's regeneration step produces a diff that the post-build no-unexpected-changes guard rejects.
wan9chi
changed the title
wan9chi
added
the
preview-build
Contributor
Registry bridge build (
|
| Package | Version |
|---|---|
vite-plus |
0.0.0-commit.fd1ae7eab160c92f3907a20e80e92d2e87403c20 |
@voidzero-dev/vite-plus-core |
0.0.0-commit.fd1ae7eab160c92f3907a20e80e92d2e87403c20 |
Install the Vite+ CLI built from this commit, then migrate a project:
# macOS / Linux
curl -fsSL https://vite.plus | VP_PR_VERSION=2081 bash# Windows (PowerShell)
$env:VP_PR_VERSION="2081"; irm https://vite.plus/ps1 | iexAfter installing, upgrade the current project's vite-plus to this test build with:
vp migrateOr point your package manager at the bridge registry https://registry-bridge.viteplus.dev/:
| Package manager | Registry config |
|---|---|
| npm / pnpm / Bun | .npmrc: registry=https://registry-bridge.viteplus.dev/ |
| Yarn (v2+) | .yarnrc.yml: npmRegistryServer: "https://registry-bridge.viteplus.dev/" |
Then pin the build (vite aliases to vite-plus-core; pnpm can use a catalog, npm an overrides entry):
{
"devDependencies": {
"vite-plus": "0.0.0-commit.fd1ae7eab160c92f3907a20e80e92d2e87403c20",
"vite": "npm:@voidzero-dev/vite-plus-core@0.0.0-commit.fd1ae7eab160c92f3907a20e80e92d2e87403c20"
}
}
Contributor
🐳 Docker preview imageBuilt from this PR's registry bridge build:
# remove any stale local copy from a previous run, then pull fresh
docker rmi ghcr.io/voidzero-dev/vite-plus:pr-2081 2>/dev/null; docker pull ghcr.io/voidzero-dev/vite-plus:pr-2081Quick check: docker run --rm ghcr.io/voidzero-dev/vite-plus:pr-2081 vp --versionSee docs/guide/docker.md for usage. |
fengmk2
added
test: e2e
wan9chi
approved these changes
Jul 7, 2026
Member
|
Discord announcement draft for v0.2.3 (copy-paste into the releases channel). Fenced so @mentions don't ping and emoji shortcodes stay literal. :viteplus: **vite-plus v0.2.3 is out** :tada:
A reliability patch for config loading, project creation, and `vp run` output, on Vite 8.1.3.
**Highlights**
:hammer_and_wrench: `vp` reads `vite.config.ts` correctly when `defineConfig` comes from a preset or custom wrapper (no more false `Task "build" not found`)
:sparkles: Ctrl-C during `vp run` no longer leaves stray escape sequences in your terminal
:hammer_and_wrench: Custom `VP_HOME` is honored on every run
:package: Bundled Vite updated to 8.1.3
**Also in this release**
- `vp create @org:name` works on registries that strip custom package fields (e.g. GitHub Packages)
- `vp migrate` emits a single `--check` when rewriting prettier scripts
- Env vars missing at runtime return `undefined` instead of `null` under `vp run`
**Bundled versions**
vite `8.1.3`, rolldown `1.1.4`, tsdown `0.22.3`, vitest `4.1.9`, oxlint `1.72.0`, oxlint-tsgolint `0.24.0`, oxfmt `0.57.0`
**Upgrade**: `vp upgrade`
Full notes: <https://github.com/voidzero-dev/vite-plus/releases/tag/v0.2.3>
Thanks to new contributors [@wan-kong](https://github.com/wan-kong) and [@hiro-daikin](https://github.com/hiro-daikin) :wave: |
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
2 participants
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.
Release vite-plus v0.2.3: config extraction, create, and
vp runreliability fixes.A patch release that restores static config extraction for projects importing
defineConfigfromvite, 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: v0.2.2...v0.2.3
Merging this PR will trigger the release workflow.