Add top-level --version / -v flag (print installed CLI version)

[renezander030]

Summary

There's no top-level capcut --version / capcut -v to print the installed CLI version. Note that the existing capcut version subcommand does something different — it inspects a draft's CapCut/JianYing support status, not the package version. A standard --version flag is what users and bug reports expect.

What to do

In src/index.ts, handle --version / -v as a global flag before command dispatch (the command is read as positional[0] after flag parsing). Print the version from package.json and exit 0.

• Resolve package.json relative to the compiled entry point. The file already computes a cliDir (used to locate templates/_init); reuse that to read ../package.json so it works from dist/.
• Add a -v, --version line to the HELP constant near the top of src/index.ts.

Example:

$ capcut --version
0.6.0

Acceptance

• capcut --version and capcut -v both print the package version and exit 0.
• Doesn't collide with the existing version subcommand (that keeps its current draft-support behavior).
• Add a test under test/ following the existing *.test.mjs pattern (helpers in test/helpers/).
• Update README.md / docs/ usage.

Pointers (verified against master)

• Single entry point src/index.ts (TypeScript → dist/); no src/commands/ dir.
• HELP constant ~line 81; command dispatch reads const cmd = positional[0].
• cliDir is already used for bundled-template resolution — reuse for package.json.
• Zero runtime dependencies (Node >= 18) — keep it dependency-free.

Good first issue — tiny, self-contained, and high-value for bug reports.

[adityabhatkar23]

@renezander030 i would like to work on this issue

[renezander030]

Thanks for jumping in, @adityabhatkar23 — assigned to you! 🙏

A few pointers so your PR sails through CI on the first try:

• Read the installed version from package.json, resolved relative to the compiled entry point. src/index.ts already computes cliDir (it uses it to locate templates/_init) — reuse that to read ../package.json so it works from dist/.
• Handle --version / -v as a global flag before command dispatch (the command is read as positional[0] after flag parsing). Don't collide with the existing version subcommand — that one inspects a draft's support status and should keep its current behavior.
• Add a -v, --version line to the HELP constant near the top of src/index.ts.
• Please include a small test under test/ (*.test.mjs, helpers in test/helpers/).

CI runs Biome lint + node --test across Node 18/20/22, so run npm test and npm run lint locally before pushing. Shout if anything's unclear — happy to help you get it merged.

[adityabhatkar23]

@renezander030 Quick question: I've implemented the feature and tests. For the README/docs update, is there a specific section where you'd like --version / - v documented ?

[renezander030]

Nice — glad the feature + tests are done! 🎉 For the docs, two light spots:

1. ## Install section — right after the install command, add a quick "verify it worked" line. This is the most natural home, since --version is the canonical post-install sanity check:

   capcut --version    # prints the installed version, e.g. 0.6.0

2. The HELP constant in src/index.ts — add a -v, --version line under the global flags (alongside -H/--human and -q/--quiet), described as "print the installed CLI version".

One small thing to avoid confusion in the docs: we already have a version subcommand (it inspects a draft's CapCut/JianYing support status). So in whatever line you add, make it clear --version/-v prints the CLI version, to keep it distinct from the subcommand. A short parenthetical is plenty.

If you've also got the docs/ command reference handy, a one-liner there is welcome too, but the two spots above are the important ones. Looking forward to the PR — thanks for the clean work!