cleanup

Author: handleyj

createReactWpTheme.js

@@ -41,18 +41,13 @@ const fs = require('fs-extra');
 const path = require('path');
 const execSync = require('child_process').execSync;
 const spawn = require('cross-spawn');
-const semver = require('semver');
 const dns = require('dns');
-const tmp = require('tmp');
-const unpack = require('tar-pack').unpack;
 const url = require('url');
-const hyperquest = require('hyperquest');
 const envinfo = require('envinfo');
-const os = require('os');
 
 const packageJson = require('./package.json');
 const _wpThemeVersion = packageJson.version;
-const _createReactAppVersion = _wpThemeVersion.split('-')[0];
+// const _createReactAppVersion = _wpThemeVersion.split('-')[0];
 
 // Check this!!!!
 const _getScriptsPath = function() {
@@ -184,7 +179,7 @@ function printValidationResults(results) {
   }
 }
 
-console.log(program.name() + " version: " + chalk.magenta(packageJson.version));
+console.log(program.name() + " version: " + chalk.magenta(_wpThemeVersion));
 createApp(
   projectName,
   program.verbose,
@@ -212,7 +207,7 @@ function createApp(
   console.log(`Creating a new React WP theme in ${chalk.green(root)}.`);
   console.log();
 
-  const useYarn = useNpm ? false : shouldUseYarn();
+  let useYarn = useNpm ? false : shouldUseYarn();
   const originalDirectory = process.cwd();
 
   process.chdir(root); // change into the newly created folder, then run create-react-app.
@@ -397,67 +392,6 @@ function getProxy() {
   }
 }
 
-function checkThatNpmCanReadCwd() {
-  const cwd = process.cwd();
-  let childOutput = null;
-  try {
-    // Note: intentionally using spawn over exec since
-    // the problem doesn't reproduce otherwise.
-    // `npm config list` is the only reliable way I could find
-    // to reproduce the wrong path. Just printing process.cwd()
-    // in a Node process was not enough.
-    childOutput = spawn.sync('npm', ['config', 'list']).output.join('');
-  } catch (err) {
-    // Something went wrong spawning node.
-    // Not great, but it means we can't do this check.
-    // We might fail later on, but let's continue.
-    return true;
-  }
-  if (typeof childOutput !== 'string') {
-    return true;
-  }
-  const lines = childOutput.split('\n');
-  // `npm config list` output includes the following line:
-  // "; cwd = C:\path\to\current\dir" (unquoted)
-  // I couldn't find an easier way to get it.
-  const prefix = '; cwd = ';
-  const line = lines.find(line => line.indexOf(prefix) === 0);
-  if (typeof line !== 'string') {
-    // Fail gracefully. They could remove it.
-    return true;
-  }
-  const npmCWD = line.substring(prefix.length);
-  if (npmCWD === cwd) {
-    return true;
-  }
-  console.error(
-    chalk.red(
-      `Could not start an npm process in the right directory.\n\n` +
-        `The current directory is: ${chalk.bold(cwd)}\n` +
-        `However, a newly started npm process runs in: ${chalk.bold(
-          npmCWD
-        )}\n\n` +
-        `This is probably caused by a misconfigured system terminal shell.`
-    )
-  );
-  if (process.platform === 'win32') {
-    console.error(
-      chalk.red(`On Windows, this can usually be fixed by running:\n\n`) +
-        `  ${chalk.cyan(
-          'reg'
-        )} delete "HKCU\\Software\\Microsoft\\Command Processor" /v AutoRun /f\n` +
-        `  ${chalk.cyan(
-          'reg'
-        )} delete "HKLM\\Software\\Microsoft\\Command Processor" /v AutoRun /f\n\n` +
-        chalk.red(`Try to run the above two lines in the terminal.\n`) +
-        chalk.red(
-          `To learn more about this problem, read: https://blogs.msdn.microsoft.com/oldnewthing/20071121-00/?p=24433/`
-        )
-    );
-  }
-  return false;
-}
-
 function checkIfOnline(useYarn) {
   if (!useYarn) {
     // Don't ping the Yarn registry.

package.json

@@ -1,6 +1,6 @@
 {
     "name": "create-react-wptheme",
-    "version": "2.1.1-wptheme-2.0.6",
+    "version": "2.1.1-wptheme-2.0.8",
     "description": "Create React WP themes with no build configuration.",
     "main": "index.js",
     "scripts": {