microsoft / microsoft/react-native-windows
Garbled output using `react-native-windows-init` with npm
Open
Nobody has claimed this yet.
Area: CLI
Area: Developer Experience
enhancement
Workstream: Developer Experience
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
In init script we call execSync('npm ...'). This API will forward any stderr (and maybe stdwarn) output from the called app. Npm emits peer dependency warnings to this output stream, so it appears in our app as well, and creates jumbled output.
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 init script and the execSync('npm ...') call described in the issue. Reproduce the command with npm peer-dependency warnings and verify that the init output is no longer forwarded in a jumbled form.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, react-native
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100