fix: rename inputs/envs to input/env (#225)

This PR standardizes the naming convention for task configuration fields
by renaming plural forms to singular forms across the codebase.

## Summary
Renamed configuration field names from plural to singular to improve
consistency and clarity:
- `inputs` → `input` (for file input patterns in cache configuration)
- `envs` → `env` (for environment variables in cache configuration)

## Key Changes

**Configuration Schema Updates:**
- Updated `EnabledCacheConfig` struct fields: `envs: Option<Box<[Str]>>`
→ `env: Option<Box<[Str]>>`
- Updated `EnabledCacheConfig` struct fields: `inputs:
Option<UserInputsConfig>` → `input: Option<UserInputsConfig>`
- Updated TypeScript type definitions in `run-config.ts` to reflect the
new field names
- Updated documentation comment for `UserInputEntry` to reference
`input` array instead of `inputs`

**Code Updates:**
- Updated all references throughout the codebase to use the new field
names
- Updated test cases and test fixtures to use `input` and `env` instead
of `inputs` and `envs`
- Updated configuration deserialization and serialization logic
- Updated default values in `UserTaskOptions::default()`
- Updated synthetic task creation in `lib.rs` and `main.rs`

**Documentation Updates:**
- Updated `task-cache.md` documentation to reference `input` and `env`
fields
- Updated `wildcard-env-patterns.md` to use `env` terminology
- Updated `CLAUDE.md` reference documentation
- Updated test snapshot descriptions and comments

**Test Fixtures:**
- Updated all `vite-task.json` fixture files to use `input` instead of
`inputs`
- Updated all `vite-task.json` fixture files to use `env` instead of
`envs`
- Updated test snapshot files and descriptions
- Updated e2e test configuration files

## Implementation Details
- The change is applied consistently across all configuration layers
(user config, resolved config, cache metadata)
- All serde deserialization/serialization updated to handle the new
field names
- Comments and documentation updated to reflect singular naming
convention
- Test names updated to match the new terminology (e.g., `test_inputs_*`
→ `test_input_*`)

https://claude.ai/code/session_01565Vu5goEjTJjXVVpvaQnb

Co-authored-by: Claude <noreply@anthropic.com>

Author: branchseer

CLAUDE.md

@@ -132,9 +132,9 @@ Tasks are defined in `vite-task.json`:
       "cwd": "relative/path",
       "dependsOn": ["build", "package#task"],
       "cache": true,
-      "envs": ["NODE_ENV"],
+      "env": ["NODE_ENV"],
       "passThroughEnvs": ["CI"],
-      "inputs": ["src/**", "!dist/**", { "auto": true }]
+      "input": ["src/**", "!dist/**", { "auto": true }]
     }
   }
 }
@@ -145,9 +145,9 @@ Tasks are defined in `vite-task.json`:
 - `cwd`: working directory relative to the package root
 - `dependsOn`: explicit task dependencies (`taskName` or `package#task`)
 - `cache` (task): enable/disable caching for this task (default: `true`)
-- `envs`: env var names to fingerprint and pass to the task
+- `env`: env var names to fingerprint and pass to the task
 - `passThroughEnvs`: env var names to pass without fingerprinting
-- `inputs`: files for cache fingerprinting (globs, `{ "auto": true }`, negation patterns)
+- `input`: files for cache fingerprinting (globs, `{ "auto": true }`, negation patterns)
 
 ## Task Dependencies
 

crates/vite_task/docs/task-cache.md

@@ -11,7 +11,7 @@ The task cache system enables:
 - **Content-based hashing**: Cache keys based on actual content, not timestamps
 - **Output replay**: Cached stdout/stderr are replayed exactly as originally produced
 - **Two-tier caching**: Cache entries shared across tasks, with task-run associations
-- **Configurable inputs**: Control which files are tracked for cache invalidation
+- **Configurable input**: Control which files are tracked for cache invalidation
 
 ### Shared caching
 
@@ -56,7 +56,7 @@ the task cache system is able to hit the same cache for the `test` task and for
 │         ▼                                                                            │
 │  2. Cache Key Generation                                                             │
 │  ──────────────────────                                                              │
-│    • Spawn fingerprint (cwd, program, args, envs)                                    │
+│    • Spawn fingerprint (cwd, program, args, env)                                    │
 │    • Input configuration                                                             │
 │         │                                                                            │
 │         ▼                                                                            │
@@ -131,15 +131,15 @@ This ensures cache invalidation when:
 
 The `fingerprinted_envs` field is crucial for cache correctness:
 
-- Only includes envs explicitly declared in the task's `envs` array
+- Only includes env vars explicitly declared in the task's `env` array
 - Does NOT include pass-through envs (PATH, CI, etc.)
-- These envs become part of the cache key
+- These env vars become part of the cache key
 
 When a task runs:
 
-1. All envs (including pass-through) are available to the process
-2. Only declared envs affect the cache key
-3. If a declared env changes value, cache will miss
+1. All env vars (including pass-through) are available to the process
+2. Only declared env vars affect the cache key
+3. If a declared env var changes value, cache will miss
 4. If a pass-through env changes, cache will still hit
 
 The `pass_through_envs` field stores env names (not values) — if the set of pass-through env names changes, the cache invalidates, but value changes don't.
@@ -220,13 +220,13 @@ Vite Task uses `fspy` to monitor file system access during task execution:
 
 ### 7. Inputs Configuration
 
-The `inputs` field in `vite-task.json` controls which files are tracked for cache fingerprinting:
+The `input` field in `vite-task.json` controls which files are tracked for cache fingerprinting:
 
 ```json
 {
   "tasks": {
     "build": {
-      "inputs": ["src/**", "!dist/**", { "auto": true }]
+      "input": ["src/**", "!dist/**", { "auto": true }]
     }
   }
 }
@@ -382,7 +382,7 @@ Cache entries are automatically invalidated when:
 4. **Pass-through config changes**: Pass-through environment names added/removed from configuration
 5. **Input files change**: Content hash differs (detected via xxHash3)
 6. **File structure changes**: Files added, removed, or type changed
-7. **Input config changes**: The `inputs` configuration itself changes
+7. **Input config changes**: The `input` configuration itself changes
 
 ## Configuration
 
@@ -535,13 +535,13 @@ Ensure commands produce identical outputs for identical inputs:
 }
 ```
 
-### 3. Use `inputs` for Precise Cache Control
+### 3. Use `input` for Precise Cache Control
 
 ```json
 {
   "tasks": {
     "build": {
-      "inputs": ["src/**", "tsconfig.json", "!src/**/*.test.ts"]
+      "input": ["src/**", "tsconfig.json", "!src/**/*.test.ts"]
     }
   }
 }

crates/vite_task/docs/wildcard-env-patterns.md

@@ -1,4 +1,4 @@
-# Common Wildcard Pattern for Task Envs
+# Common Wildcard Pattern for Task Env
 
 ## Executive Summary
 
@@ -13,7 +13,7 @@ Currently, vite-plus requires explicit listing of environment variables in task
   "tasks": {
     "build": {
       "command": "vite build",
-      "envs": ["NODE_ENV", "NODE_OPTIONS", "VITE_API_URL", "VITE_APP_TITLE", "MY_APP_PORT"]
+      "env": ["NODE_ENV", "NODE_OPTIONS", "VITE_API_URL", "VITE_APP_TITLE", "MY_APP_PORT"]
     }
   }
 }
@@ -23,7 +23,7 @@ This approach becomes cumbersome when dealing with multiple environment variable
 
 ## Goals
 
-1. **Simplify Configuration**: Allow wildcard patterns in the `envs` array to match multiple environment variables
+1. **Simplify Configuration**: Allow wildcard patterns in the `env` array to match multiple environment variables
 2. **Maintain Cache Correctness**: Ensure wildcard-matched variables are properly included in cache fingerprints
 3. **Backward Compatibility**: Support both explicit variable names and wildcard patterns
 4. **Performance**: Minimal overhead when resolving environment variables
@@ -32,7 +32,7 @@ This approach becomes cumbersome when dealing with multiple environment variable
 ## Non-Goals
 
 1. Full regex support (only glob-style wildcards)
-2. Wildcard patterns in `pass_through_envs` (same as `envs`)
+2. Wildcard patterns in `passThroughEnvs` (same as `env`)
 3. Complex glob patterns like `{VITE,NODE}_*` (supported by wax crate)
 
 ## Proposed Solution
@@ -63,7 +63,7 @@ We don't support `!` for negated patterns. If match the negated pattern, will ig
 ```
 ┌─────────────────┐
 │  Task Config    │
-│   envs: [       │
+│   env: [       │
 │     "NODE_*",   │
 │     "VITE_*",   │
 │     "CI"        │
@@ -164,7 +164,7 @@ pub struct CommandFingerprint {
   "tasks": {
     "build": {
       "command": "vite build",
-      "envs": [
+      "env": [
         "NODE_ENV",
         "NODE_OPTIONS",
         "VITE_API_URL",
@@ -184,7 +184,7 @@ pub struct CommandFingerprint {
   "tasks": {
     "build": {
       "command": "vite build",
-      "envs": ["NODE_*", "VITE_*"]
+      "env": ["NODE_*", "VITE_*"]
     }
   }
 }

crates/vite_task/src/session/cache/display.rs

@@ -173,7 +173,7 @@ pub fn format_cache_status_inline(cache_status: &CacheStatus) -> Option<Str> {
                         None => "configuration changed",
                     }
                 }
-                FingerprintMismatch::InputConfig => "inputs configuration changed",
+                FingerprintMismatch::InputConfig => "input configuration changed",
                 FingerprintMismatch::InputChanged { kind, path } => {
                     let desc = format_input_change_str(*kind, path.as_str());
                     return Some(vite_str::format!("✗ cache miss: {desc}, executing"));

crates/vite_task/src/session/cache/mod.rs

@@ -119,7 +119,7 @@ impl Display for FingerprintMismatch {
                 write!(f, "Spawn fingerprint changed: old={old:?}, new={new:?}")
             }
             Self::InputConfig => {
-                write!(f, "inputs configuration changed")
+                write!(f, "input configuration changed")
             }
             Self::InputChanged { kind, path } => {
                 write!(f, "{}", display::format_input_change_str(*kind, path.as_str()))

crates/vite_task/src/session/reporter/summary.rs

@@ -439,7 +439,7 @@ impl TaskResult {
                         }
                     }
                     SavedCacheMissReason::ConfigChanged => {
-                        Str::from("→ Cache miss: inputs configuration changed")
+                        Str::from("→ Cache miss: input configuration changed")
                     }
                     SavedCacheMissReason::InputChanged { kind, path } => {
                         let desc = format_input_change_str(*kind, path.as_str());

crates/vite_task_bin/src/lib.rs

@@ -62,9 +62,9 @@ fn synthesize_node_modules_bin_task(
         program: find_executable(get_path_env(envs), cwd, executable_name)?,
         args: args.into(),
         cache_config: UserCacheConfig::with_config(EnabledCacheConfig {
-            envs: None,
+            env: None,
             pass_through_envs: None,
-            inputs: None,
+            input: None,
         }),
         envs: Arc::clone(envs),
     })
@@ -127,9 +127,9 @@ impl vite_task::CommandHandler for CommandHandler {
                     args: [name.clone()].into(),
                     cache_config: UserCacheConfig::with_config({
                         EnabledCacheConfig {
-                            envs: None,
+                            env: None,
                             pass_through_envs: Some(vec![name]),
-                            inputs: None,
+                            input: None,
                         }
                     }),
                     envs: Arc::new(envs),

crates/vite_task_bin/src/main.rs

@@ -33,9 +33,9 @@ async fn run() -> anyhow::Result<ExitStatus> {
                     args: [Str::from("FOO")].into(),
                     cache_config: UserCacheConfig::with_config({
                         EnabledCacheConfig {
-                            envs: Some(Box::from([Str::from("FOO")])),
+                            env: Some(Box::from([Str::from("FOO")])),
                             pass_through_envs: None,
-                            inputs: None,
+                            input: None,
                         }
                     }),
                     envs: Arc::clone(envs),

crates/vite_task_bin/tests/e2e_snapshots/fixtures/cache-miss-reasons/snapshots.toml

@@ -61,10 +61,10 @@ steps = [
 ]
 
 [[e2e]]
-name = "inputs config changed"
+name = "input config changed"
 steps = [
   "vp run test # cache miss",
-  "json-edit vite-task.json \"_.tasks.test.inputs = ['test.txt']\" # change inputs config",
+  "json-edit vite-task.json \"_.tasks.test.input = ['test.txt']\" # change input config",
   "vp run test # cache miss: configuration changed",
 ]
 

…ons/snapshots/inputs config changed.snap …sons/snapshots/input config changed.snapcrates/vite_task_bin/tests/e2e_snapshots/fixtures/cache-miss-reasons/snapshots/inputs config changed.snap renamed to crates/vite_task_bin/tests/e2e_snapshots/fixtures/cache-miss-reasons/snapshots/input config changed.snap crates/vite_task_bin/tests/e2e_snapshots/fixtures/cache-miss-reasons/snapshots/inputs config changed.snap renamed to crates/vite_task_bin/tests/e2e_snapshots/fixtures/cache-miss-reasons/snapshots/input config changed.snap

@@ -5,8 +5,8 @@ expression: e2e_outputs
 > vp run test # cache miss
 $ print-file test.txt
 initial content
-> json-edit vite-task.json "_.tasks.test.inputs = ['test.txt']" # change inputs config
+> json-edit vite-task.json "_.tasks.test.input = ['test.txt']" # change input config
 
 > vp run test # cache miss: configuration changed
-$ print-file test.txt ✗ cache miss: inputs configuration changed, executing
+$ print-file test.txt ✗ cache miss: input configuration changed, executing
 initial content