403f356082
Summary: On windows, recent versions of local-cli will display a yarn error to stderr when starting the packager (see https://github.com/expo/xde/issues/91, https://github.com/react-community/create-react-native-app/issues/101, https://github.com/react-community/create-react-native-app/issues/113#issuecomment-289185491 for examples of users hitting this in the wild), even though no package management action is being taken. From what I can tell this is what happens: * [`local-cli/util/yarn.js` does not ignore stderr on Windows]( |
||
---|---|---|
.. | ||
__mocks__ | ||
Config.js | ||
PackageManager.js | ||
assertRequiredOptions.js | ||
copyAndReplace.js | ||
findSymlinksPaths.js | ||
isPackagerRunning.js | ||
isValidPackageName.js | ||
log.js | ||
parseCommandLine.js | ||
walk.js | ||
yarn.js |