Windows build fails due to `chmod` command not recognized

[Kieutran26]

Environment

• OS: Windows 11
• Node: v24.11.1
• pnpm: 10.x

Problem

Running pnpm -r build fails on Windows because the CLI package
build script uses chmod +x dist/bin.js, which is not a valid
command on Windows.

Error

'chmod' is not recognized as an internal or external command,
operable program or batch file.
ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL @html-video/cli@0.1.0 build

Suggested Fix

Replace chmod +x dist/bin.js with a cross-platform solution:

• Use shx package: shx chmod +x dist/bin.js
• Or add a Windows-compatible script in package.json

[lefarcen]

Hi @Kieutran26! Thanks for the clear Windows repro — the pnpm -r build failure makes sense from what’s in the repo.

The CLI package currently runs tsc -p tsconfig.json && chmod +x dist/bin.js in packages/cli/package.json, so this is a real cross-platform build bug rather than a local setup issue. On Windows, that plain chmod step is the part that breaks. A cross-platform replacement like shx chmod +x dist/bin.js or a tiny Node-based postbuild step should be enough here.

I’ve triaged this as a bug and marked it as a good community issue since the fix looks nicely scoped. If you want to open a PR for it, we’d be happy to review.

[lefarcen]

If anyone in the community wants to take this on, comment /claim and we’ll mark it as yours for follow-up.

[kacimiamine]

/claim

[lefarcen]

Thanks for picking this up, @kacimiamine — it’s yours. What timeline feels realistic on your side: a few hours, 1–3 days, around a week, or longer?

[kacimiamine]

A few minutes, I already have the fix

[kacimiamine]

@lefarcen You can check the PR now, thank you!

[lefarcen]

Heads-up: PR #34 is now open for this Windows build bug.

It removes the plain chmod +x dist/bin.js step from packages/cli/package.json, which is the command causing pnpm -r build to fail on Windows. We’ll track implementation review in #34, and this issue stays open until that PR lands.

[lefarcen]

Re-opening this issue for community contribution because linked PR #34 has had no author activity.

The PR has been left open as draft so @kacimiamine can resume later, and others may /claim this issue if they want to take it on.