| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
✅ Deploy Preview for viteplus-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Sorry, something went wrong.
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.
|
Discord announcement draft (concise), copy-paste after the release is published: **Vite+ Beta is out (vite-plus v0.2.2)** :tada:
Stable, production-ready, MIT. Read the announcement: https://voidzero.dev/posts/announcing-vite-plus-beta
**Highlights**
:seedling: `vp migrate` now upgrades existing Vite+ projects across versions
:hammer_and_wrench: Official Docker image: `ghcr.io/voidzero-dev/vite-plus`
:zap: Zero-config `vp build` caching (auto outputs + tracked envs)
:lock: PGP-verified Node.js downloads
**Also in this release**
- `check.fmt` / `check.lint` config for `vp check`
- `vpr` ships as a package bin (works on Vercel/CI)
- Windows: `vp run` no longer hangs on PowerShell `.cmd` shims
- Task cache survives switching branches across Vite+ versions
- `dependsOn: [{ task, from: "dependencies" }]`
**Bundled versions**
vite `8.1.2`, 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.2>
Thanks to new contributors @rokuosan, @Aalivexy, @cheezone, @daflyinbed, @forehalo, @kvnwolf :wave: |
Sorry, something went wrong.
|
vite-plus
npm i https://pkg.pr.new/voidzero-dev/vite-plus@2016
npm i https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-core@2016
npm i https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-prompts@2016
npm i https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-cli-darwin-arm64@2016
npm i https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-cli-darwin-x64@2016
npm i https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-cli-linux-arm64-gnu@2016
npm i https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-cli-linux-arm64-musl@2016
npm i https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-cli-linux-x64-gnu@2016
npm i https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-cli-linux-x64-musl@2016
npm i https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-cli-win32-arm64-msvc@2016
npm i https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-cli-win32-x64-msvc@2016
npm i https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-darwin-arm64@2016
npm i https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-darwin-x64@2016
npm i https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-linux-arm64-gnu@2016
npm i https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-linux-arm64-musl@2016
npm i https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-linux-x64-gnu@2016
npm i https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-linux-x64-musl@2016
npm i https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-win32-arm64-msvc@2016
npm i https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-win32-x64-msvc@2016 commit: 1d7ba81 |
Sorry, something went wrong.
Registry bridge build (1d7ba81)This commit is published to pkg.pr.new and registered with the registry bridge, which serves these as ordinary npm versions (every other package proxies to npmjs):
Install the Vite+ CLI built from this commit, then migrate a project: # macOS / Linux
curl -fsSL https://vite.plus | VP_PR_VERSION=2016 bash# Windows (PowerShell)
$env:VP_PR_VERSION="2016"; 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/:
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.1d7ba811f0e456640b0e761e8e8acf77d1ad3251",
"vite": "npm:@voidzero-dev/vite-plus-core@0.0.0-commit.1d7ba811f0e456640b0e761e8e8acf77d1ad3251"
}
} |
Sorry, something went wrong.
🐳 Docker preview imageBuilt from this PR's pkg.pr.new build:
# remove any stale local copy from a previous run, then pull fresh
docker rmi ghcr.io/voidzero-dev/vite-plus:pr-2016 2>/dev/null; docker pull ghcr.io/voidzero-dev/vite-plus:pr-2016Quick check: docker run --rm ghcr.io/voidzero-dev/vite-plus:pr-2016 vp --versionSee docs/guide/docker.md for usage. |
Sorry, something went wrong.
Documents the v0.2.2 (PR #2016) smoke test run: choosing a target project pinned to the previous release for a real upgrade path, passing the full build commit SHA when the PR head has moved, the shape of a passing run, and the single-version pass criteria with the release-blocker rule on failure.
There was a problem hiding this comment.
BETA!
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Release vite-plus v0.2.2: the Vite+ Beta release.
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
Features
Fixes & Enhancements
Refactor
Docs
Chore
Bundled Versions
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: v0.2.1...v0.2.2
Merging this PR will trigger the release workflow.