You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: prefer system npm/npx over project-local versions from node_modules (#1172)
When the CLI runs inside an npm script (or any context where
node_modules/.bin is on PATH), getNpxBinPath() could pick up a
project-local npx instead of the system one. The standalone npx package
(npx@10.2.2) bundles npm@5.1.0 which is incompatible with Node 22+,
causing "cb.apply is not a function" errors during Coana reachability
analysis.
Fix: check for npm/npx next to process.execPath (the running node
binary) before falling back to PATH-based lookup. This follows the same
pattern already used by findRealNpm() in @socketsecurity/registry and
getAgentExecPath() in package-environment.mts.
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
0 commit comments