fix(cli): fall back to NAPI when plugins are present in vite config (#1213)

resolve #1211 

When a Vite plugin adds `run.tasks` via the `config` hook,
`VitePlusConfigLoader` was skipping the NAPI-based `resolveConfig()`,
because the static analyzer found no `run` field and returned `None`
immediately, without ever executing plugin hooks.

Fix by checking for `plugins` before `run`: if plugins are present,
always fall back to NAPI so that Vite's `resolveConfig()` runs plugin
`config` hooks. When no plugins are present, static analysis results
remain trustworthy and the fast path is preserved.

Author: kazupon

packages/cli/binding/src/cli.rs

@@ -620,25 +620,37 @@ impl UserConfigLoader for VitePlusConfigLoader {
     ) -> anyhow::Result<Option<UserRunConfig>> {
         // Try static config extraction first (no JS runtime needed)
         let static_fields = vite_static_config::resolve_static_config(package_path);
-        match static_fields.get("run") {
-            Some(vite_static_config::FieldValue::Json(run_value)) => {
-                tracing::debug!(
-                    "Using statically extracted run config for {}",
-                    package_path.as_path().display()
-                );
-                let run_config: UserRunConfig = serde_json::from_value(run_value)?;
-                return Ok(Some(run_config));
-            }
-            Some(vite_static_config::FieldValue::NonStatic) => {
-                // `run` field exists (or may exist via a spread) — fall back to NAPI
-                tracing::debug!(
-                    "run config is not statically analyzable for {}, falling back to NAPI",
-                    package_path.as_path().display()
-                );
-            }
-            None => {
-                // Config was analyzed successfully and `run` field is definitively absent
-                return Ok(None);
+
+        // If plugins are present, a plugin's config hook may add/modify the `run`
+        // field at runtime, so we must fall back to NAPI-based resolution which
+        // calls Vite's resolveConfig() and executes plugin hooks.
+        if static_fields.get("plugins").is_some() {
+            tracing::debug!(
+                "plugins detected for {}, falling back to NAPI to run config hooks",
+                package_path.as_path().display()
+            );
+        } else {
+            // No plugins — static analysis results are trustworthy
+            match static_fields.get("run") {
+                Some(vite_static_config::FieldValue::Json(run_value)) => {
+                    tracing::debug!(
+                        "Using statically extracted run config for {}",
+                        package_path.as_path().display()
+                    );
+                    let run_config: UserRunConfig = serde_json::from_value(run_value)?;
+                    return Ok(Some(run_config));
+                }
+                Some(vite_static_config::FieldValue::NonStatic) => {
+                    // `run` field exists (or may exist via a spread) — fall back to NAPI
+                    tracing::debug!(
+                        "run config is not statically analyzable for {}, falling back to NAPI",
+                        package_path.as_path().display()
+                    );
+                }
+                None => {
+                    // Config was analyzed successfully and `run` field is definitively absent
+                    return Ok(None);
+                }
             }
         }
 

packages/cli/snap-tests/vite-config-task-from-plugin/package.json

@@ -0,0 +1,4 @@
+{
+  "name": "vite-config-task-from-plugin-test",
+  "private": true
+}

packages/cli/snap-tests/vite-config-task-from-plugin/snap.txt

@@ -0,0 +1,5 @@
+> # Test that tasks added by a plugin config hook are recognized by vp run
+> vp run build:prod
+$ echo 'build:prod from plugin config hook' ⊘ cache disabled
+build:prod from plugin config hook
+

packages/cli/snap-tests/vite-config-task-from-plugin/steps.json

@@ -0,0 +1,6 @@
+{
+  "commands": [
+    "# Test that tasks added by a plugin config hook are recognized by vp run",
+    "vp run build:prod"
+  ]
+}

packages/cli/snap-tests/vite-config-task-from-plugin/vite.config.ts

@@ -0,0 +1,20 @@
+function myTaskPlugin() {
+  return {
+    name: 'my-task-plugin',
+    config() {
+      return {
+        run: {
+          tasks: {
+            'build:prod': {
+              command: "echo 'build:prod from plugin config hook'",
+            },
+          },
+        },
+      };
+    },
+  };
+}
+
+export default {
+  plugins: [myTaskPlugin()],
+};