Improve CLI usage documentation on windows

[breautek]

On windows using Command Prompt or Powershell, when we need to use the intermediate -- to pass through arguments, the -- needs to be enclosed in quotations

For example:

cordova build android --release "--" --packageType=apk

All of our examples show MacOS / Linux usage. This is something I personally help people resolve in discussions/slack, but can also be a source of bug reports.

Below is a list of links that I found that uses pass through CLI args, but this list may not be exhaustive.

https://cordova.apache.org/docs/en/12.x/reference/cordova-cli/index.html
https://cordova.apache.org/docs/en/12.x/guide/platforms/android/index.html

[breautek]

Alternatively instead of having a "windows" and "unix/bash" version of the command line, cordova build android --release "--" --packageType=apk does appear to work in bash environments as well. So avoid creating too much verbosity we could just show all CLI examples to use the "--" separator, with the quotations.

[dheeraj12347]

Hi, @breautek

From your description, on Windows (Command Prompt/PowerShell) the pass‑through separator needs to be written as "--" so that arguments are forwarded correctly, for example:

cordova build android --release "--" --packageType=apk

Currently, the examples in the documentation (such as the CLI reference and Android platform guide) only show the Unix/macOS style without quotes. This can be confusing for Windows users and has already led to related bug reports.

My proposed approach is:

Update all Cordova CLI examples that demonstrate pass‑through arguments so they consistently use "--" in the command, e.g. cordova build android --release "--" --packageType=apk.

Add a short note near the first such example explaining that on Windows the separator must be quoted, and that the quoted form also works correctly on Unix/macOS shells.

Make these changes in the relevant docs pages you referenced in this issue (and any other occurrences I find), keeping the wording and formatting consistent with the existing documentation.

If this approach aligns with what you have in mind, I would be happy and grateful to work on this issue and open a PR.