mirror of
https://github.com/status-im/react-native.git
synced 2025-01-10 17:45:59 +00:00
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](6fa87134fc/local-cli/util/yarn.js (L25)
) * [`local-cli/util/PackageManager.js` calls the above function when it's require'd](6fa87134fc/local-cli/util/PackageManager.js (L20)
) For Windows users who don't have yarn installed, this means that the 'yarn is not recognized as an internal or external command..." error displays wh Closes https://github.com/facebook/react-native/pull/13355 Differential Revision: D4848084 Pulled By: hramos fbshipit-source-id: f32176354e0bd7ff6d7009ea30dca64ff23ae3d5
58 lines
1.7 KiB
JavaScript
58 lines
1.7 KiB
JavaScript
/**
|
|
* Copyright (c) 2015-present, Facebook, Inc.
|
|
* All rights reserved.
|
|
*
|
|
* This source code is licensed under the BSD-style license found in the
|
|
* LICENSE file in the root directory of this source tree. An additional grant
|
|
* of patent rights can be found in the PATENTS file in the same directory.
|
|
*/
|
|
'use strict';
|
|
|
|
const execSync = require('child_process').execSync;
|
|
const fs = require('fs');
|
|
const path = require('path');
|
|
const semver = require('semver');
|
|
|
|
/**
|
|
* Use Yarn if available, it's much faster than the npm client.
|
|
* Return the version of yarn installed on the system, null if yarn is not available.
|
|
*/
|
|
function getYarnVersionIfAvailable() {
|
|
let yarnVersion;
|
|
try {
|
|
// execSync returns a Buffer -> convert to string
|
|
yarnVersion = (execSync('yarn --version', {
|
|
stdio: [ 0, 'pipe', 'ignore', ]
|
|
}).toString() || '').trim();
|
|
} catch (error) {
|
|
return null;
|
|
}
|
|
// yarn < 0.16 has a 'missing manifest' bug
|
|
try {
|
|
if (semver.gte(yarnVersion, '0.16.0')) {
|
|
return yarnVersion;
|
|
} else {
|
|
return null;
|
|
}
|
|
} catch (error) {
|
|
console.error('Cannot parse yarn version: ' + yarnVersion);
|
|
return null;
|
|
}
|
|
}
|
|
|
|
/**
|
|
* Check that 'react-native init' itself used yarn to install React Native.
|
|
* When using an old global react-native-cli@1.0.0 (or older), we don't want
|
|
* to install React Native with npm, and React + Jest with yarn.
|
|
* Let's be safe and not mix yarn and npm in a single project.
|
|
* @param projectDir e.g. /Users/martin/AwesomeApp
|
|
*/
|
|
function isGlobalCliUsingYarn(projectDir) {
|
|
return fs.existsSync(path.join(projectDir, 'yarn.lock'));
|
|
}
|
|
|
|
module.exports = {
|
|
getYarnVersionIfAvailable: getYarnVersionIfAvailable,
|
|
isGlobalCliUsingYarn: isGlobalCliUsingYarn,
|
|
};
|