Merge branch 'main' into feat/cli-completion

Author: fengmk2

.github/actions/build-upstream/action.yml

@@ -43,11 +43,11 @@ runs:
           target/${{ inputs.target }}/release/vp-shim.exe
         key: ${{ steps.cache-key.outputs.key }}
 
-    # Apply Vite+ branding patches to rolldown-vite source (CI checks out
-    # upstream rolldown-vite which doesn't have branding patches)
-    - name: Brand rolldown-vite
+    # Apply Vite+ branding patches to vite source (CI checks out
+    # upstream vite which doesn't have branding patches)
+    - name: Brand vite
       shell: bash
-      run: pnpm exec tool brand-rolldown-vite
+      run: pnpm exec tool brand-vite
 
     # Build upstream TypeScript packages first (don't depend on native bindings)
     - name: Build upstream TypeScript packages

.github/actions/clone/action.yml

@@ -15,12 +15,12 @@ outputs:
 runs:
   using: 'composite'
   steps:
-    - name: Output rolldown and rolldown-vite hash
+    - name: Output rolldown and vite hash
       shell: bash
       id: upstream-versions
       run: |
         node -e "console.log('ROLLDOWN_HASH=' + require('./packages/tools/.upstream-versions.json').rolldown.hash)" >> $GITHUB_OUTPUT
-        node -e "console.log('ROLLDOWN_VITE_HASH=' + require('./packages/tools/.upstream-versions.json')['rolldown-vite'].hash)" >> $GITHUB_OUTPUT
+        node -e "console.log('ROLLDOWN_VITE_HASH=' + require('./packages/tools/.upstream-versions.json')['vite'].hash)" >> $GITHUB_OUTPUT
 
     - name: Output ecosystem ci project hash
       shell: bash
@@ -40,7 +40,7 @@ runs:
     - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
       with:
         repository: vitejs/vite
-        path: rolldown-vite
+        path: vite
         ref: ${{ steps.upstream-versions.outputs.ROLLDOWN_VITE_HASH }}
 
     # Disable autocrlf to preserve LF line endings on Windows

.github/renovate.json

@@ -7,7 +7,7 @@
     "packages/cli/snap-tests-todo/**",
     "bench/fixtures/**",
     "rolldown/**",
-    "rolldown-vite/**"
+    "vite/**"
   ],
   "packageRules": [
     {

.github/scripts/upgrade-deps.mjs

@@ -48,8 +48,8 @@ async function updateUpstreamVersions() {
   // rolldown -> rolldown/rolldown
   data.rolldown.hash = await getLatestTagCommit('rolldown', 'rolldown');
 
-  // rolldown-vite -> vitejs/vite
-  data['rolldown-vite'].hash = await getLatestTagCommit('vitejs', 'vite');
+  // vite -> vitejs/vite
+  data['vite'].hash = await getLatestTagCommit('vitejs', 'vite');
 
   fs.writeFileSync(filePath, JSON.stringify(data, null, 2) + '\n');
   console.log('Updated .upstream-versions.json');

.github/workflows/claude.yml

@@ -24,15 +24,18 @@ jobs:
         uses: anthropics/claude-code-action@26ec041249acb0a944c0a47b6c0c13f05dbc5b44 # v1.0.70
         with:
           claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
-          claude_args: --allowedTools "Read,Glob,Grep,Bash(gh:*),Bash(cargo:*),Bash(git:*),WebFetch"
-          issue_number: ${{ github.event.issue.number }}
+          assignee_trigger: 'boshen'
+          claude_args: --allowedTools "Edit,Write,Read,Glob,Grep,Bash(gh:*),Bash(cargo:*),Bash(git:*),Bash(just:*),WebFetch,TodoWrite"
           prompt: |
-            Analyze the linked issue and determine if it can be fixed.
+            Analyze issue #${{ github.event.issue.number }} in ${{ github.repository }} and determine if it can be fixed.
 
+            First, use `gh issue view ${{ github.event.issue.number }}` to read the issue details.
+
+            Then:
             1. Search the codebase to gather relevant context (related files, existing implementations, tests)
             2. Determine if the issue is fixable and estimate the complexity
 
-            Post a comment on the issue with:
+            Finally, post a comment on the issue with:
             - A brief summary of your understanding of the issue
             - Relevant files/code you found
             - Whether this issue is fixable (yes/no/needs clarification)

.github/workflows/e2e-test.yml

@@ -251,6 +251,12 @@ jobs:
             node-version: 24
             command: |
               vp test run
+          - name: vp-config
+            node-version: 22
+            command: |
+              vp check
+              vp pack
+              vp test
         exclude:
           # frm-stack uses Docker (testcontainers) which doesn't work the same way on Windows
           - os: windows-latest

.github/workflows/upgrade-deps.yml

@@ -142,7 +142,7 @@ jobs:
           body: |
             Automated daily upgrade of upstream dependencies:
             - rolldown (latest tag)
-            - rolldown-vite (latest tag)
+            - vite (latest tag)
             - vitest (latest npm version)
             - tsdown (latest npm version)
 

.gitignore

@@ -6,4 +6,5 @@ dist
 .DS_Store
 rolldown
 rolldown-vite
+vite
 /crates/vite_global_cli/vp

ecosystem-ci/repo.json

@@ -60,5 +60,10 @@
     "branch": "main",
     "hash": "451925ad7c07750a23de1d6ed454825d0eb14092",
     "forceFreshMigration": true
+  },
+  "vp-config": {
+    "repository": "https://github.com/kazupon/vp-config.git",
+    "branch": "main",
+    "hash": "b58c48d71a17c25dec71a003535e6312791ce2aa"
   }
 }

packages/cli/BUNDLING.md

@@ -286,7 +286,7 @@ The CLI package creates thin shim files that re-export from `@voidzero-dev/vite-
 3. **Reduces duplication** - No file copying, just re-exports
 4. **Preserves module resolution** - Node.js resolves to the actual core package
 
-**Note**: The `@voidzero-dev/vite-plus-core` package itself bundles multiple upstream projects (rolldown-vite, rolldown, tsdown, vitepress). See [Core Package Bundling](../core/BUNDLING.md) for details.
+**Note**: The `@voidzero-dev/vite-plus-core` package itself bundles multiple upstream projects (vite, rolldown, tsdown, vitepress). See [Core Package Bundling](../core/BUNDLING.md) for details.
 
 ### Export Mapping (Core)