Skip to content

vp migrate beta test#4

Draft
fengmk2 wants to merge 1 commit into
mainfrom
vp-migrate-test
Draft

vp migrate beta test#4
fengmk2 wants to merge 1 commit into
mainfrom
vp-migrate-test

Conversation

@fengmk2

@fengmk2 fengmk2 commented Jun 30, 2026

Copy link
Copy Markdown
Owner

No description provided.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request migrates the repository to Vite+, a unified toolchain, replacing tsdown and standard vite/vitest configurations with vp commands and vite-plus imports across various packages and test files. Feedback highlights a redundant vp config execution in the prepare script of package.json and warns against replacing vite with vite-plus in the downloadable playground template, which would cause runtime errors for end-users.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread package.json
},
"scripts": {
"prepare": "FORCE_COLOR=1 turbo run turbo:postinstall",
"prepare": "vp config && FORCE_COLOR=1 turbo run turbo:postinstall",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The prepare script executes vp config before running turbo run turbo:postinstall. Since turbo:postinstall already executes vp config internally, this leads to vp config being run twice during the installation process. Consider removing the redundant vp config call from the prepare script to optimize the setup workflow.

Suggested change
"prepare": "vp config && FORCE_COLOR=1 turbo run turbo:postinstall",
"prepare": "FORCE_COLOR=1 turbo run turbo:postinstall",

@@ -1,4 +1,4 @@
import { defineConfig } from 'vite';
import { defineConfig } from 'vite-plus';

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Changing the import in the downloadable playground template from vite to vite-plus will cause runtime errors for end-users unless vite-plus is added to the template's package.json dependencies. Furthermore, forcing external playground users to use vite-plus instead of standard vite may be unintended. It is recommended to keep standard vite for the downloadable template.

Suggested change
import { defineConfig } from 'vite-plus';
import { defineConfig } from 'vite';

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant