feat: add create-vite-plus package

[liangmiQwQ]

Close #2602

This PR implements create-vite-plus package by calling vp create under the hood.

🤖 Generated with Claude

[liangmiQwQ]

The trusted publish needs @Boshen's configuration (cc @fengmk2)

[liangmiQwQ]

@fengmk2 is that ok to skip preview builds for this package?

[fengmk2]

The trusted publish configuration is already done! Let me start a preview build.

[fengmk2]

@codex review

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-13T15:07:49.160289Z	b4eb245	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b4eb2450b7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[github-actions]

Registry bridge build (eb1b283)

Warning

This build is from the fork liangmiQwQ/vite-plus and has not been reviewed.
Installing it runs that code on your machine. Build log

This commit build is published to the registry bridge, which serves these as ordinary npm versions (every other package proxies to npmjs):

Package	Version
vite-plus	0.0.0-commit.eb1b283e86c7daf63bfab12ea76c597bc916af09
@voidzero-dev/vite-plus-core	0.0.0-commit.eb1b283e86c7daf63bfab12ea76c597bc916af09
create-vite-plus	0.0.0-commit.eb1b283e86c7daf63bfab12ea76c597bc916af09

Install the Vite+ CLI built from this commit, then migrate a project:

# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/liangmiQwQ/vite-plus/eb1b283e86c7daf63bfab12ea76c597bc916af09/packages/cli/install.sh | VP_PR_VERSION=3028 VP_LEGACY_INSTALLER_URL=https://raw.githubusercontent.com/liangmiQwQ/vite-plus/eb1b283e86c7daf63bfab12ea76c597bc916af09/packages/cli/install-legacy.sh bash

# Windows (PowerShell)
$env:VP_PR_VERSION="3028"; $env:VP_LEGACY_INSTALLER_URL="https://raw.githubusercontent.com/liangmiQwQ/vite-plus/eb1b283e86c7daf63bfab12ea76c597bc916af09/packages/cli/install-legacy.ps1"; irm https://raw.githubusercontent.com/liangmiQwQ/vite-plus/eb1b283e86c7daf63bfab12ea76c597bc916af09/packages/cli/install.ps1 | iex

Or download the standalone Windows installer built from this commit:

Architecture	Installer
x64	vp-setup-x86_64-pc-windows-msvc.exe
Arm64	vp-setup-aarch64-pc-windows-msvc.exe

GitHub requires you to sign in and downloads each installer as a ZIP artifact. Extract vp-setup.exe, then run it against this preview build:

.\vp-setup.exe --version "0.0.0-commit.eb1b283e86c7daf63bfab12ea76c597bc916af09" --registry "https://registry-bridge.viteplus.dev/"

After installing, upgrade the current project's vite-plus to this test build with:

vp migrate

Or create a new project from this commit without installing the CLI:

export npm_config_registry=https://registry-bridge.viteplus.dev/ pnpm_config_registry=https://registry-bridge.viteplus.dev/
pnpm create vite-plus@0.0.0-commit.eb1b283e86c7daf63bfab12ea76c597bc916af09 # or: npm create vite-plus@0.0.0-commit.eb1b283e86c7daf63bfab12ea76c597bc916af09

$env:npm_config_registry="https://registry-bridge.viteplus.dev/"; $env:pnpm_config_registry="https://registry-bridge.viteplus.dev/"
pnpm create vite-plus@0.0.0-commit.eb1b283e86c7daf63bfab12ea76c597bc916af09 # or: npm create vite-plus@0.0.0-commit.eb1b283e86c7daf63bfab12ea76c597bc916af09

pnpm 11+ reads pnpm_config_registry, npm and older pnpm read npm_config_registry. The new project pins this build, so keep the registry set for later installs, or configure it as below.

Or 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.eb1b283e86c7daf63bfab12ea76c597bc916af09",
    "vite": "npm:@voidzero-dev/vite-plus-core@0.0.0-commit.eb1b283e86c7daf63bfab12ea76c597bc916af09"
  }
}

[fengmk2]

@liangmiQwQ Can you update the content of the preview build comment #3028 (comment) to add usage instructions for create-vite-plus?

[fengmk2]

I will merge after the preview build success and test pass.