test(e2e): clarify vite env cache fixture

Co-authored-by: GPT-5 Codex <codex@openai.com>

Author: wan9chi

crates/vite_task_bin/tests/e2e_snapshots/fixtures/vite_build_cache/snapshots.toml

@@ -1,7 +1,7 @@
 [[e2e]]
 name = "vite_prefix_env_change_invalidates_cache"
 comment = """
-`VITE_MODE` is picked up by Vite's patched `loadEnv`, which asks the runner for every `VITE_*` env via `getEnvs(pattern, { tracked: true })`. Flipping its value between runs must invalidate the cache AND change the build output — Vite's `define` plugin substitutes `import.meta.env.VITE_MODE` at build time, so dead-code elimination leaves only the branch matching the value.
+`VITE_CACHE_LABEL` is picked up by Vite's patched `loadEnv`, which asks the runner for every `VITE_*` env via `getEnvs(pattern, { tracked: true })`. Flipping its value between runs must invalidate the cache AND change the build output because Vite substitutes `import.meta.env.VITE_CACHE_LABEL` at build time.
 """
 ignore = true
 steps = [
@@ -12,56 +12,56 @@ steps = [
     "build",
   ], envs = [
     [
-      "VITE_MODE",
-      "production",
+      "VITE_CACHE_LABEL",
+      "cache-alpha",
     ],
-  ], comment = "first run: production build" },
+  ], comment = "first run: cache-alpha label" },
   { argv = [
     "vtt",
     "grep-file",
     "dist/assets/main.js",
-    "BUILD_MODE_PROD",
-  ], comment = "production build: PROD marker survived DCE" },
+    "cache-alpha",
+  ], comment = "cache-alpha label is in the bundle" },
   { argv = [
     "vtt",
     "grep-file",
     "dist/assets/main.js",
-    "BUILD_MODE_DEV",
-  ], comment = "dev branch is gone" },
+    "cache-bravo",
+  ], comment = "cache-bravo label is not in the bundle yet" },
   { argv = [
     "vt",
     "run",
     "--cache",
     "build",
   ], envs = [
     [
-      "VITE_MODE",
-      "production",
+      "VITE_CACHE_LABEL",
+      "cache-alpha",
     ],
-  ], comment = "cache hit: VITE_MODE unchanged" },
+  ], comment = "cache hit: VITE_CACHE_LABEL unchanged" },
   { argv = [
     "vt",
     "run",
     "--cache",
     "build",
   ], envs = [
     [
-      "VITE_MODE",
-      "development",
+      "VITE_CACHE_LABEL",
+      "cache-bravo",
     ],
-  ], comment = "cache miss: envs changed — VITE_MODE value changed" },
+  ], comment = "cache miss: envs changed — VITE_CACHE_LABEL value changed" },
   { argv = [
     "vtt",
     "grep-file",
     "dist/assets/main.js",
-    "BUILD_MODE_PROD",
-  ], comment = "PROD marker gone after the dev rebuild" },
+    "cache-alpha",
+  ], comment = "cache-alpha label is gone after the rebuild" },
   { argv = [
     "vtt",
     "grep-file",
     "dist/assets/main.js",
-    "BUILD_MODE_DEV",
-  ], comment = "DEV marker now in the bundle" },
+    "cache-bravo",
+  ], comment = "cache-bravo label is now in the bundle" },
 ]
 
 [[e2e]]
@@ -105,4 +105,3 @@ steps = [
     ],
   ], comment = "cache miss: envs changed (NODE_ENV changed)" },
 ]
-

crates/vite_task_bin/tests/e2e_snapshots/fixtures/vite_build_cache/snapshots/vite_prefix_env_change_invalidates_cache.md

@@ -1,34 +1,34 @@
 # vite_prefix_env_change_invalidates_cache
 
-`VITE_MODE` is picked up by Vite's patched `loadEnv`, which asks the runner for every `VITE_*` env via `getEnvs(pattern, { tracked: true })`. Flipping its value between runs must invalidate the cache AND change the build output — Vite's `define` plugin substitutes `import.meta.env.VITE_MODE` at build time, so dead-code elimination leaves only the branch matching the value.
+`VITE_CACHE_LABEL` is picked up by Vite's patched `loadEnv`, which asks the runner for every `VITE_*` env via `getEnvs(pattern, { tracked: true })`. Flipping its value between runs must invalidate the cache AND change the build output because Vite substitutes `import.meta.env.VITE_CACHE_LABEL` at build time.
 
-## `VITE_MODE=production vt run --cache build`
+## `VITE_CACHE_LABEL=cache-alpha vt run --cache build`
 
-first run: production build
+first run: cache-alpha label
 
 ```
 $ vite build
 ```
 
-## `vtt grep-file dist/assets/main.js BUILD_MODE_PROD`
+## `vtt grep-file dist/assets/main.js cache-alpha`
 
-production build: PROD marker survived DCE
+cache-alpha label is in the bundle
 
 ```
-dist/assets/main.js: found "BUILD_MODE_PROD"
+dist/assets/main.js: found "cache-alpha"
 ```
 
-## `vtt grep-file dist/assets/main.js BUILD_MODE_DEV`
+## `vtt grep-file dist/assets/main.js cache-bravo`
 
-dev branch is gone
+cache-bravo label is not in the bundle yet
 
 ```
-dist/assets/main.js: missing "BUILD_MODE_DEV"
+dist/assets/main.js: missing "cache-bravo"
 ```
 
-## `VITE_MODE=production vt run --cache build`
+## `VITE_CACHE_LABEL=cache-alpha vt run --cache build`
 
-cache hit: VITE_MODE unchanged
+cache hit: VITE_CACHE_LABEL unchanged
 
 ```
 $ vite build ◉ cache hit, replaying
@@ -37,26 +37,26 @@ $ vite build ◉ cache hit, replaying
 vt run: cache hit.
 ```
 
-## `VITE_MODE=development vt run --cache build`
+## `VITE_CACHE_LABEL=cache-bravo vt run --cache build`
 
-cache miss: envs changed — VITE_MODE value changed
+cache miss: envs changed — VITE_CACHE_LABEL value changed
 
 ```
-$ vite build ○ cache miss: env 'VITE_MODE' changed, executing
+$ vite build ○ cache miss: env 'VITE_CACHE_LABEL' changed, executing
 ```
 
-## `vtt grep-file dist/assets/main.js BUILD_MODE_PROD`
+## `vtt grep-file dist/assets/main.js cache-alpha`
 
-PROD marker gone after the dev rebuild
+cache-alpha label is gone after the rebuild
 
 ```
-dist/assets/main.js: missing "BUILD_MODE_PROD"
+dist/assets/main.js: missing "cache-alpha"
 ```
 
-## `vtt grep-file dist/assets/main.js BUILD_MODE_DEV`
+## `vtt grep-file dist/assets/main.js cache-bravo`
 
-DEV marker now in the bundle
+cache-bravo label is now in the bundle
 
 ```
-dist/assets/main.js: found "BUILD_MODE_DEV"
+dist/assets/main.js: found "cache-bravo"
 ```

crates/vite_task_bin/tests/e2e_snapshots/fixtures/vite_build_cache/src/main.js

@@ -1,9 +1,3 @@
-// `import.meta.env.VITE_MODE` is replaced at build time from the value vite
-// picks up for keys matching `envPrefix` (`VITE_` by default). The markers
-// let the e2e test assert that flipping VITE_MODE actually changed what was
-// built and that glob-tracking invalidates the cache.
-if (import.meta.env.VITE_MODE === 'production') {
-  document.body.append('BUILD_MODE_PROD');
-} else {
-  document.body.append('BUILD_MODE_DEV');
-}
+// Vite replaces this at build time from keys matching `envPrefix` (`VITE_` by
+// default), so the e2e can verify that glob-tracked env changes rebuild output.
+console.log(import.meta.env.VITE_CACHE_LABEL);