Skip to content

fix(cli): execute jest javascript entrypoint directly and add config unit tests - #2262

Open
VG31OP wants to merge 1 commit into
ruvnet:mainfrom
VG31OP:fix/cli-test-script-jest-entrypoint
Open

VG31OP wants to merge 1 commit into
ruvnet:mainfrom
VG31OP:fix/cli-test-script-jest-entrypoint

Conversation

@VG31OP

@VG31OP VG31OP commented Oct 13, 2026

Copy link
Copy Markdown

Summary

  • In tools/ruview-cli/package.json, the "test" script specified node --experimental-vm-modules node_modules/.bin/jest.
    • On platforms like Windows (or npm installs where .bin/jest is a shell wrapper script rather than a symlink), passing node_modules/.bin/jest directly to the node binary fails with SyntaxError: missing ) after argument list.
    • Aligns tools/ruview-cli/package.json with tools/ruview-mcp/package.json by invoking the actual JavaScript entry point node_modules/jest/bin/jest.js.
    • Adds unit tests in tools/ruview-cli/tests/config.test.ts covering loadConfig() defaults and environment overrides.

Verification

  • npm test in tools/ruview-cli exits 0 (2 passed).
    • npm run typecheck in tools/ruview-cli exits 0.
    • npm run build in tools/ruview-cli exits 0.
    • npm test in tools/ruview-mcp exits 0 (112 passed).
    • npm test in harness/homecore exits 0 (27 passed).

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant