Sounds like bansai

How about using the child_process module? const {spawn} = require('child_process') const proc = spawn('ssh', ['example.com', 'cmd to run']) ...

Oh, I see why I was confused: you are using an old version of React (Codepen's version is 0.13). In this version, in order to get a reference to the DOM node from the React ref, you have to use "getDOMNode()": this.refs.list.getDOMNode().value In updated versions of React, this is not necessary.

You registered the <select> element to have a ref of "list", thus the correct path would be: this.refs. list .value

Short answer: the core of Node.JS is multithreaded, but all user-code (i.e., JavaScript that you write) is single-threaded. Node.JS spawns multiple threads (allocated strictly for I/O operations), gathers their results and then posts each result back to the one/main/single thread. So it depends on your perspective, if you will: From the point of the JavaScript developer, Node.JS is single threaded. From the perspective of Node.JS core (libuv), it is multi-threaded. Multithreaded, but...

I feel like webpack-chain is a monolith, and still looks a bit unwieldy. I put together webpack-configify in order to simplify my "typical" webpack config, with the option of just dropping in and merging webpack config using the ".merge(...)" function for the more specific things one might want to do with webpack config.

I am not an authority on this, but my impression was that Chess algorithms use a combination of techniques: Openings database - the algorithm will keep a database of known good opening moves that get it to a certain point Brute force - try to predict all possible combinations of moves up until some future point (only do this for the next, say, 10, moves); keep track of the path that maximizes your chances for victory Here is an interesting read from StackExchange .

I developed a solution for my own use, which in turn makes use of Juho Vepsäläinen 's webpack-merge: const builder = require ( 'webpack-configify' ).default const prod = process.env.NODE_ENV == 'production' module .exports = builder() .production(prod) .development(!prod) .src( './src/index.js' ) .dest( './build' , false ) .loader( '.js' , 'babel-loader' ) .merge({output: {publicPath: '/build/' }}) .build() if ( require .main === module ) // eslint-disable-next-line no-console console .log( require ( 'util' ).inspect( module .exports, null , null ))