Remove cra prefix from craSourceWorkspaces, now sourceWorkspaces.

Author: bradfordlemley

packages/react-dev-utils/workspaceUtils.js

@@ -38,7 +38,7 @@ const findMonorepo = appDir => {
   const workspaces = monoPkg && monoPkg.workspaces;
   const patterns = (workspaces && workspaces.packages) || workspaces;
   const isYarnWs = Boolean(patterns);
-  const srcPatterns = appPkg && appPkg.craSourceWorkspaces;
+  const srcPatterns = appPkg && appPkg.sourceWorkspaces;
   const allPkgs = patterns && findPkgs(path.dirname(monoPkgPath), patterns);
   const allSrcPkgs =
     srcPatterns && findPkgs(path.dirname(monoPkgPath), srcPatterns);

packages/react-scripts/fixtures/monorepos/yarn-ws/packages/cra-app1/package.json

@@ -30,7 +30,7 @@
       "not ie < 11"
     ]
   },
-  "craSourceWorkspaces": [
+  "sourceWorkspaces": [
     "packages/comp*"
   ]
 }

packages/react-scripts/template/README.md

@@ -1885,7 +1885,7 @@ monorepo/
       "devDependencies": {
         "react-scripts": "2.0.0"
       },
-      "craSourceWorkspaces" : [
+      "sourceWorkspaces" : [
         "comp*"
       ]
     src/
@@ -1899,7 +1899,7 @@ monorepo/
       "devDependencies": {
         "react-scripts": "2.0.0"
       },
-      "craSourceWorkspaces" : [
+      "sourceWorkspaces" : [
         "comp*"
       ]
     src/
@@ -1923,7 +1923,7 @@ monorepo/
 ```
 * Monorepo tools work on a package level, the same level as an npm package.
 * The "workspaces" entry in the top-level package.json is an array of glob patterns specifying where shared packages are located in the monorepo.
-* The "craSourceWorkspaces" entry in an app's package.json is array of glob patterns similar to "workspaces", but specifying which packages in the monorepo should be treated as source.
+* The "sourceWorkspaces" entry in an app's package.json is array of glob patterns similar to "workspaces", but specifying which packages in the monorepo should be treated as source.
 * The scoping prefixes, e.g. @myorg/, are not required, but are recommended, allowing you to differentiate your packages from others of the same name.  See [scoped packages ](https://docs.npmjs.com/misc/scope) for more info.
 * Using a package in the monorepo is accomplished in the same manner as a published npm package, by specifying the shared package as dependency.
 * In order to pick up the monorepo version of a package, the specified dependency version must semantically match the package version in the monorepo.  See [semver](https://docs.npmjs.com/misc/semver) for info on semantic version matching.