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
Hello! I am running auto in an environment where I don't have npx installed (only Node and Yarn). And I am getting the following error when running auto shipit:
/bin/sh: npx: not found
at ChildProcess.<anonymous> (/srv/workspace/node_modules/@auto-it/core/src/utils/exec-promise.ts:76:23)
at ChildProcess.emit (events.js:315:20)
at ChildProcess.EventEmitter.emit (domain.js:467:12)
at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)Error:
at Object.execPromise (/srv/workspace/node_modules/@auto-it/core/src/utils/exec-promise.ts:17:20)
at /srv/workspace/node_modules/@auto-it/npm/src/index.ts:691:17
at _next0 (eval at create (/srv/workspace/node_modules/tapable/lib/HookCodeFactory.js:75:10), <anonymous>:18:1)
at eval (eval at create (/srv/workspace/node_modules/tapable/lib/HookCodeFactory.js:75:10), <anonymous>:34:1)
To Reproduce
Run auto shipit in an environment which lacks of npm and npx
Expected behavior
To be able to run auto shipit on environments that doesn't have npx. This could be solved by checking if a yarn.lock exists (and run yarn lerna), elsewere, default to npx.
Thanks for the report @elkevinwolf. It's a good callout. We actually changed it to be this way in #1936 😄. Obviously we should be more defensive in checking to ensure a particular sub-tool exists before relying on it.
Describe the bug
Hello! I am running
auto
in an environment where I don't havenpx
installed (only Node and Yarn). And I am getting the following error when runningauto shipit
:To Reproduce
auto shipit
in an environment which lacks ofnpm
andnpx
Expected behavior
To be able to run
auto shipit
on environments that doesn't havenpx
. This could be solved by checking if ayarn.lock
exists (and runyarn lerna
), elsewere, default tonpx
.Screenshots
N/A
Environment information:
Additional context
N/A
The text was updated successfully, but these errors were encountered: