Uh oh!
There was an error while loading. Please reload this page.
refactor(env)!: rename VITE_PLUS_* env vars to VP_* prefix - #1166
Conversation
✅ Deploy Preview for viteplus-preview canceled.
|
| else | ||
| INSTALL_BASH="curl -fsSL https://vite.plus | VITE_PLUS_VERSION=${{ env.VERSION }} bash" | ||
| INSTALL_PS1="\\\$env:VITE_PLUS_VERSION=\\\"${{ env.VERSION }}\\\"; irm https://vite.plus/ps1 | iex" | ||
| INSTALL_BASH="curl -fsSL https://vite.plus | VP_VERSION=${{ env.VERSION }} bash" |
Check notice
Code scanning / zizmor
code injection via template expansion Note
| INSTALL_BASH="curl -fsSL https://vite.plus | VITE_PLUS_VERSION=${{ env.VERSION }} bash" | ||
| INSTALL_PS1="\\\$env:VITE_PLUS_VERSION=\\\"${{ env.VERSION }}\\\"; irm https://vite.plus/ps1 | iex" | ||
| INSTALL_BASH="curl -fsSL https://vite.plus | VP_VERSION=${{ env.VERSION }} bash" | ||
| INSTALL_PS1="\\\$env:VP_VERSION=\\\"${{ env.VERSION }}\\\"; irm https://vite.plus/ps1 | iex" |
Check notice
Code scanning / zizmor
code injection via template expansion Note
jong-kyung
commented
Mar 27, 2026
@codex review |
8adb819 to
194e940CompareThere was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:8adb8192e5
ℹ️ 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".
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
194e940 to
ae89367CompareUh oh!
There was an error while loading. Please reload this page.
jong-kyung
commented
Mar 28, 2026
There's currently a merge conflict with main. If there are no further changes needed, I'll squash the fixup commits and resolve the conflict. |
jong-kyung
commented
Mar 28, 2026
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:9057048a3f
ℹ️ 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".
Uh oh!
There was an error while loading. Please reload this page.
fengmk2
left a comment
There was a problem hiding this comment.
@jong-kyung good job! Please resolve the conflicts, I will manually verifying and then merge on Monday.
9057048 to
e5b2f05Compare7ef75ea to
e78b07cComparefengmk2
commented
Mar 29, 2026
@jong-kyung After I merged the main branch code, CI fails now. Could you help me take a look? |
jong-kyung
commented
Mar 29, 2026
Sure, I will check It |
jong-kyung
commented
Mar 29, 2026
The CI failure was caused by #1185 ( Updated the test to use the renamed |
Set both VP_VERSION (new) and VITE_PLUS_VERSION (legacy) when invoking the install script, so the action works with vite-plus versions before and after the VP_* env var rename. Ref: voidzero-dev/vite-plus#1166
Uh oh!
There was an error while loading. Please reload this page.
## Summary - Set both `VP_VERSION` (new) and `VITE_PLUS_VERSION` (legacy) env vars when invoking the vite-plus install script - Ensures the action works with vite-plus versions before and after the `VP_*` env var rename (voidzero-dev/vite-plus#1166) - Includes a TODO comment to remove `VITE_PLUS_VERSION` once old versions are no longer supported ## Test plan - [x] CI passes with current vite-plus release (reads `VITE_PLUS_VERSION`) - [x] After voidzero-dev/vite-plus#1166 merges, verify install still works (reads `VP_VERSION`) 🤖 Generated with [Claude Code](https://claude.ai/claude-code) --------- Signed-off-by: MK (fengmk2) <fengmk2@gmail.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
After #1166, all VITE_PLUS_<env_var> env vars are renamed to VP_<env_var>. When I read RFCs, I found some RFCs still include deprecated `VITE_PLUS_` env vars. In this PR, I let Codex find and update all of them.
## Summary This follows up on #1166, which renamed `VITE_PLUS_*` environment variables to use the `VP_*` prefix. It applies the same convention to the remaining Vite+-specific variables: `VITE_LOG`, `VITE_GLOBAL_CLI_JS_SCRIPTS_DIR`, and `VITE_UPDATE_TASK_TYPES`, without retaining compatibility aliases. Resolves#2206
Summary
Closes#1074
Rename all internal
VITE_PLUS_*environment variables toVP_*prefix to avoid Vite's defaultenvPrefix: "VITE_"from exposing them in bundled applications viaimport.meta.env.get_vite_plus_home()→get_vp_home()to matchdocs/guide/env.md)VITE_LOG,VITE_NODE_DIST_MIRROR,VITE_UPDATE_TASK_TYPES,VITE_GLOBAL_CLI_JS_SCRIPTS_DIR— these use theVITE_prefix (notVITE_PLUS_) and are intentionally keptPrerequisite (merged)
VP_*toDEFAULT_UNTRACKED_ENVso internal vars pass through to child processes without affecting cache keysPlease let me know if I missed anything — I'll fix it.