refactor(env): rename remaining Vite+ environment variables

[jong-kyung]

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

[netlify]

✅ Deploy Preview for viteplus-preview canceled.

Name	Link
🔨 Latest commit	096bdab
🔍 Latest deploy log	https://app.netlify.com/projects/viteplus-preview/deploys/6a7155a04559cf0008f24654

[jong-kyung]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. 🎉

Reviewed commit: f97c1b1368

ℹ️ 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".

[fengmk2]

The VITE_UPDATE_TASK_TYPES environment variable doesn't seem to be used anywhere? I didn't see it being set anywhere.

[jong-kyung]

The VITE_UPDATE_TASK_TYPES environment variable doesn't seem to be used anywhere? I didn't see it being set anywhere.

It is read in packages/cli/binding/src/cli/mod.rs. I wasn't sure whether it should be renamed or removed, so I left it out of this PR and raised the question here.

vite-plus/packages/cli/binding/src/cli/mod.rs

Lines 460 to 480 in d1183bd

	#[test]
	fn run_config_types_in_sync() {
	// Remove \r for cross-platform consistency
	let ts_type = UserRunConfig::TS_TYPE.replace('\r', "");
	let manifest_dir = std::env::var("CARGO_MANIFEST_DIR").expect("CARGO_MANIFEST_DIR not set");
	let run_config_path = PathBuf::from(manifest_dir).join("../src/run-config.ts");
	if std::env::var("VITE_UPDATE_TASK_TYPES").as_deref() == Ok("1") {
	std::fs::write(&run_config_path, &ts_type).expect("Failed to write run-config.ts");
	} else {
	let current = std::fs::read_to_string(&run_config_path)
	.expect("Failed to read run-config.ts")
	.replace('\r', "");
	pretty_assertions::assert_eq!(
	current,
	ts_type,
	"run-config.ts is out of sync. Run `VITE_UPDATE_TASK_TYPES=1 cargo test -p vite-plus-cli run_config_types_in_sync` to update."
	);
	}
	}
	}

[fengmk2]

It is read in packages/cli/binding/src/cli/mod.rs. I wasn't sure whether it should be renamed or removed, so I left it out of this PR and raised the question here.

Here, we are just reading VITE_UPDATE_TASK_TYPES, but it needs to be confirmed where it is set.

[jong-kyung]

I couldn't find anywhere in the repository that sets it either. It appears to be intended as a developer flag. Should we remove it? 🤔

[fengmk2]

I couldn't find anywhere in the repository that sets it either. It appears to be intended as a developer flag. Should we remove it? 🤔

Sure, go ahead and delete it with a new PR.

cc @wan9chi

[jong-kyung]

Renamed VITE_UPDATE_TASK_TYPES to VP_UPDATE_TASK_TYPES while preserving the manual regeneration flow.
Context: #2315 (comment)