saucelabs / saucelabs/node-saucectl
On failure yarn gives no output but npm does
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 9
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Expected Behavior
When the install fails on yarn it should return the output of the error.
Actual Behavior
In yarn the build does not show the error:
error ..../node_modules/saucectl: Command failed.
Output:
With npm it will give more info:
Installation failed:
Check that you have access to https://github.com/saucelabs/saucectl/releases or format of the
SAUCECTL_INSTALL_BINARY environment variable is correct
Steps to Reproduce the Problem
- In my case, the error is happening because I'm on an M1 Mac and saucectl dependencies don't detect it correctly.
- Add saucectl as a dependency in package.json.
- Run
yarn
Specifications
- Version:
- saucectl, tried with both 0.87.0 and 0.102.0
- yarn 1.22.19
- node 16.14.2
- Platform: Apple M1 processor, MacBook Pro, macOS 12.14 (monterey)
- Subsystem:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure by adding saucectl to package.json and running yarn on the stated Node.js and macOS setup, then compare the output with npm. Trace where the installation error is emitted and confirm that yarn exposes the underlying error details, including the access or SAUCECTL_INSTALL_BINARY guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100