[Tarte12]

Closes #3140

• Document that FOO=bar command works on Windows without cross-env for commands Vite Task parses directly.
• Clarify that a prefix applies only to the command it precedes in && chains.
• Document shell fallback (/bin/sh -c / cmd.exe /d /s /c) and that it applies to the whole command.
• Fix the command reference, which implied every command runs through a shell.

Behavior is based on the vite-task source (9ba4cc9, linked in the issue). Not tested on Windows.

[hyunbinseo]

After reviewing, I think Vite Task should document how it parses commands first, so these docs can link to it instead of describing internals. This goes beyond env prefixes: it decides cross-platform behavior and whether && chains become cached sub-tasks.

I'll open a vite-task issue to spec it alongside task-cache.md.

[jong-kyung]

cc @wan9chi

[hyunbinseo]

Shouldn't the Vite Task parsing be placed on the top of vpr docs (e.g. as a note block)?

I don't think this explanation applies to "Environment Variable Prefixes" only.

[hyunbinseo]

Why not use a vanilla non-vp command inside the build script?

[hyunbinseo]

These seem to be implementation details. It would be nice if Vite Task had documentation of these that can be linked to? Or at least it should be converted to a warning block, etc.

[hyunbinseo]

"Work as written" isn't true on Windows when it falls back to cmd.exe (e.g. single quotes, $VAR). Same as the guide, it'd be nice to link to Vite Task docs for the parsing rules. Until then, how about:

Suggested change

	Defines the command to run for the task. Quoting, `&&`, pipes, and redirects all work as written on the command line. Vite Task runs simple commands and `&&` chains directly, and falls back to the system shell for other shell syntax. See [Environment Variable Prefixes](/guide/run#environment-variable-prefixes) for details.
	Defines the command to run for the task. Vite Task parses simple commands and `&&` chains itself, so they behave the same on every platform. Other shell syntax, such as pipes and redirects, runs in the system shell: `/bin/sh` on macOS and Linux, and `cmd.exe` on Windows. See [Environment Variable Prefixes](/guide/run#environment-variable-prefixes) for details.

[hyunbinseo]

Line 120 is now inconsistent: && is only split into cached sub-tasks when parsed, not on shell fallback. Array entries are always split. Maybe update it too?

[hyunbinseo]

@jong-kyung How should we proceed? I would love to out-link Vite Task behaviors as mentioned above. The PR can be polished for review once it is decided.

[jong-kyung]

Personally, I think it would be better not to link to the Vite Task docs

[hyunbinseo]

Thanks for the quick reply. We'll drop the detailed Vite Task behavior and keep the PR focused on:

1. Simple commands are parsed by Vite+ (Vite Task) directly.
2. One benefit: FOO=bar command works on Windows without cross-env.
3. A prefix applies only to the command it directly precedes. The docs will also note that other behaviors (e.g. shell fallback) exist and should be verified at runtime.