Make test:integration runnable outside a POSIX shell

[nedonatelli]

npm run test:integration inlined four things cmd.exe does not have, so the entire integration suite was unrunnable on Windows:

rm -rf out/src/test/integration && ... && { find src -name '*.js' \
  -not -path 'src/test/*' -delete 2>/dev/null || true; } && vscode-test

npm runs scripts through cmd.exe on Windows, where rm and find do not exist, /dev/null is not a path, and { ...; } is not a group. Verified directly rather than assumed:

cmd /c "rm -rf out/src/test/integration"
-> 'rm' is not recognized as an internal or external command

Same class as the mkdir -p in copy-grammars (3c1bae3), which silently skipped every tree-sitter suite instead of failing — that one cost real coverage before anyone noticed.

What changed

scripts/integration-clean.mjs in two modes, replacing the shell steps:

• pre — remove the previous integration build output
• post — prune stray compiled .js outside src/test, swallowing per-file errors to match the || true the shell version ended with. A stray file that cannot be removed must not fail the test run.

How it was found

Audited all 40 npm scripts for POSIX-only constructs after two of them turned out to be broken on Windows. This was the only remaining one. The two other regex hits were false positives — cross-env already handles a second VAR= on the same line.

🤖 Generated with Claude Code

[github-actions]

✅ All checks passed

Check	Status
Type check	✅ success
Lint	✅ success
Tests	✅ success

Posted by SideCarAI-Bot