Skip to content
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.

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

npx not found #1983

Closed
kevinwolfcr opened this issue May 19, 2021 · 1 comment
Closed

npx not found #1983

kevinwolfcr opened this issue May 19, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@kevinwolfcr
Copy link
Contributor

Describe the bug

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.

Screenshots

N/A

Environment information:

Environment Information:

"auto" version: v10.28.0
"git"  version: v2.30.2
"node" version: v14.16.1

Project Information:

✔ Repository:      elkevinwolf/devtools (​https://github.com/elkevinwolf/devtools​)
✔ Author Name:     Kevin Wolf
✔ Author Email:    hi@kevinwolf.dev
✖ Current Version: v
✔ Latest Release:  @elkevinwolf/prettier-config@1.0.0 (​https://github.com/elkevinwolf/devtools/releases/tag/%40elkevinwolf/prettier-config%401.0.0​)

✔ Labels configured on GitHub project 

GitHub Token Information:

✔ Token:            [Token starting with ghp_]
✔ Repo Permission:  admin
✔ User:             elkevinwolf
✔ API:              undefined (​undefined​)
✔ Enabled Scopes:   admin:enterprise, admin:gpg_key, admin:org, admin:org_hook, admin:public_key, admin:repo_hook, delete:packages, delete_repo, gist, notifications, repo, user, workflow, write:discussion, write:packages
✔ Rate Limit:       4985/5000

Additional context

N/A

@kevinwolfcr kevinwolfcr added the bug Something isn't working label May 19, 2021
@zephraph
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants