fix: use runtime execPath for MCP bridge #101

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open

OrdinarySF wants to merge 1 commit into slopus:main from OrdinarySF:fix/runtime-mcp

+18 −12

OrdinarySF commented Dec 24, 2025

Summary

Use the active runtime (Node or Bun) to launch the MCP bridge and CLI, improving compatibility when running under Bun or a custom runtime path.

Changes

MCP bridge now uses process.execPath as the command and passes the bridge script path as the first arg.
CLI spawn resolves runtime from HAPPY_NODE_BIN or process.execPath, with Bun detection by version/basename.
Node-only flags are skipped for Bun, and the resolved runtime is logged for debugging.

Risk / Notes

Runtime path falls back to node if no execPath is available.
Bun detection depends on process.versions.bun or runtime basename containing bun.


          fix: use runtime execPath for MCP bridge

babb51b

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

Labels

None yet