microsoft / microsoft/vscode-react-native
[Feature] EAS config command swallows CLI errors
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.7k
- Forks
- 295
- Avg merge
- 11h 17m
- Merged PRs (30d)
- 24
Description
Problem
When eas build:configure --platform all fails, the command catches every error and only logs that the app may not be linked to an EAS project.
This hides the original error and may provide misleading guidance for failures such as a missing CLI, network issues, or permission errors.
Expected behavior
The command should log the existing user-facing guidance and rethrow the original error so it can be reported and diagnosed correctly.
Proposed change
- Rethrow the original error after logging the EAS project guidance.
- Add a regression test verifying that command execution errors are preserved.
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
Start by locating the TypeScript implementation and existing tests for eas build:configure --platform all. Read the error-handling path and its current EAS project guidance, then add a regression test that makes command execution fail and verifies the original error is preserved after the guidance is logged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 75/100