Skip to content

Prefer which node over process.execPath to find out node path#19

Open
luisdeltoro wants to merge 1 commit intodifferent-ai:mainfrom
luisdeltoro:main
Open

Prefer which node over process.execPath to find out node path#19
luisdeltoro wants to merge 1 commit intodifferent-ai:mainfrom
luisdeltoro:main

Conversation

@luisdeltoro
Copy link
Copy Markdown

resolveNodePath() previously prioritised process.execPath, which on Homebrew resolves to a versioned Cellar path (e.g. /opt/homebrew/Cellar/node/25.8.1/bin/node). This path breaks silently after a brew upgrade node, causing the native messaging host to fail to launch and the Chrome extension to lose its connection.

This fix swaps the resolution order so which node (or where node on Windows) is tried first. Package managers like Homebrew, nvm, fnm, and volta all expose a stable symlink (e.g. /opt/homebrew/bin/node) via PATH, which survives upgrades. process.execPath is kept as a fallback for environments where which may not be available.

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.

2 participants