[Bryandero98]

Fixes #158

Root cause

src/runtime.ts captured process.argv once, when the module was imported (runtimeProcessArgs = process.argv), and parse() used that value when called without arguments.

Runners such as vite-node load cac for their own CLI first and only afterwards replace process.argv for the script they run. With a single shared cac instance (same version resolved for the runner and the app) the app's cli.parse() sees the array from import time, which still contains the script path. That path ends up in args and the matched command never runs, which is the behaviour in the issue.

Reproduction

Not tied to a particular version of cac or vite-node: it needs the runner and the app to share one cac instance.

• cac@6.7.14 + vite-node@2.1.9: npx vite-node index.ts hello prints {"args":["index.ts","hello"],...} and no Hello World! (the report in The behavior of the "parse" function when used without arguments is strange. #158).
• cac@7.0.0 + vite-node@6 (which depends on cac 7): same result.
• With this change, the second case prints Hello World! and {"args":[],...}.

Change

getRuntimeProcessArgs() returns process.argv at call time (or undefined where there is no process), and parse() uses it. The runtimeInfo handling is untouched.

Test

tests/index.test.ts has a plain unit test that replaces process.argv after cac was imported and checks that parse() reads the new value. It does not depend on vite-node. It fails on main (rawArgs is the stale array) and passes with the change; the full suite passes (21 tests) and tsc --noEmit is clean.