📚 multi-processing w/ Node Cluster API

* Add npm 5’s `package-lock.json`

* Upgrade deployment to Node 6.11

* Fix react-ui build command to work with npm 5.

* Revise react-ui build to honor lock file for production dependencies

README.md

@@ -10,7 +10,7 @@ To deploy a frontend-only React app, use the static-site optimized
 
 ## Design Points
 
-A combo of two npm projects, the backend server and the frontend UI. So there are two `package.json` configs.
+A combo of two npm projects, the backend server and the frontend UI. So there are two `package.json` configs and thereforce two places to run `npm` commands:
 
   1. [`package.json`](package.json) for [Node server](server/) & [Heroku deploy](https://devcenter.heroku.com/categories/deployment)
       * `heroku-postbuild` script compiles the webpack bundle during deploy
@@ -18,6 +18,7 @@ A combo of two npm projects, the backend server and the frontend UI. So there ar
   2. [`react-ui/package.json`](react-ui/package.json) for [React web UI](react-ui/)
       * generated by [create-react-app](https://github.com/facebookincubator/create-react-app)
 
+Includes a minimal [Node Cluster](https://nodejs.org/docs/latest-v8.x/api/cluster.html) [implementation](server/index.js) to parallelize the single-threaded Node process across the available CPU cores.
 
 ## Demo
 
@@ -43,6 +44,8 @@ This deployment will automatically:
     * serves `../react-ui/build/` as static files
     * customize by adding API, proxy, or route handlers/redirectors
 
+⚠️ Using npm 5’s new `package-lock.json`? We resolved a compatibility issue. See [PR](https://github.com/mars/heroku-cra-node/pull/10) for more details.
+
 👓 More about [deploying to Heroku](https://devcenter.heroku.com/categories/deployment).
 
 

app.json

@@ -0,0 +1,21 @@
+{
+  "name": "heroku-cra-node",
+  "description": "web app made of create-react-app UI + Node API",
+  "scripts": {
+  },
+  "env": {
+  },
+  "formation": {
+    "web": {
+      "quantity": 1
+    }
+  },
+  "addons": [
+
+  ],
+  "buildpacks": [
+    {
+      "url": "heroku/nodejs"
+    }
+  ]
+}

package.json

@@ -3,7 +3,7 @@
   "version": "1.0.0",
   "description": "How to use create-react-app with a custom Node API on Heroku",
   "engines": {
-    "node": "6.11.x"
+    "node": "8.9.x"
   },
   "scripts": {
     "start": "node server",

react-ui/package.json

@@ -3,11 +3,11 @@
   "version": "0.1.0",
   "private": true,
   "devDependencies": {
-    "react-scripts": "0.9.5"
+    "react-scripts": "^1.1.0"
   },
   "dependencies": {
-    "react": "^15.4.2",
+    "react": "^16.2.0",
-    "react-dom": "^15.4.2"
+    "react-dom": "^16.2.0"
   },
   "scripts": {
     "start": "react-scripts start",

server/index.js

@@ -1,9 +1,26 @@
 const express = require('express');
 const path = require('path');
+const cluster = require('cluster');
+const numCPUs = require('os').cpus().length;
 
-const app = express();
 const PORT = process.env.PORT || 5000;
 
+// Multi-process to utilize all CPU cores.
+if (cluster.isMaster) {
+  console.error(`Node cluster master ${process.pid} is running`);
+
+  // Fork workers.
+  for (let i = 0; i < numCPUs; i++) {
+    cluster.fork();
+  }
+
+  cluster.on('exit', (worker, code, signal) => {
+    console.error(`Node cluster worker ${worker.process.pid} exited: code ${code}, signal ${signal}`);
+  });
+
+} else {
+  const app = express();
+
   // Priority serve any static files.
   app.use(express.static(path.resolve(__dirname, '../react-ui/build')));
 
@@ -19,5 +36,6 @@ app.get('*', function(request, response) {
   });
 
   app.listen(PORT, function () {
-  console.log(`Listening on port ${PORT}`);
+    console.error(`Node cluster worker ${process.pid}: listening on port ${PORT}`);
   });
+}