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

CLI: 'yarn' is not recognized as ... message for operations on Windows #14081

Closed
FLGMwt opened this issue May 21, 2017 · 0 comments
Closed

CLI: 'yarn' is not recognized as ... message for operations on Windows #14081

FLGMwt opened this issue May 21, 2017 · 0 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@FLGMwt
Copy link
Contributor

FLGMwt commented May 21, 2017

Description

Suspected source origin of issue in react-vr: facebookarchive/react-360#203

When invoking react-init on Windows when yarn isn't present on the system, the error message from the check is output.

Reproduction Steps and Sample Code

List all the steps required to reproduce the issue you're reporting. These steps should be clear and concise.

Example:

> react-native init foo
This will walk you through creating a new React Native project in C:\git\react-native-1\react-native-cli\foo
'yarn' is not recognized as an internal or external command,
operable program or batch file.
Installing react-native...
Consider installing yarn to make this faster: https://yarnpkg.com

Expected behavior is that this output should be muted.

Solution

Similar to facebookarchive/react-360#204, the output can simply be piped to 2> NUL, eg yarn --version 2> NUL.

Additional Information

  • React Native version: cli version 2.0.1
  • Platform: CLI on Windows
  • Development Operating System: Windows
  • Dev tools: Confirmed in PowerShell & CMD
@facebook facebook locked as resolved and limited conversation to collaborators May 29, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants