Mitigate redux-form console noise in the interim until we upgrade

Ah, right — because the `redux-form` we want to have included was obtained from GitHub rather than an NPM release. Makes perfect sense.

1. we need uglify-webpack-plugin because the yarn build step fails without it.

2. we need yarn build because stripes depends on build artifacts of redux-form, not on its source code. This is analogous to running make install (or sudo apt-get install ..., etc) to install shared libraries like APR and whatever you need for PCRE in mod-rewrite before you compile apache (something else I used to do in the previous millennium).

Yep, I got com from CVS, too!

Come to think of it, why do we even need yarn build? Why doesn't it suffice for the desired version of redux-form to be in the workspace, so it gets picked up ahead of whatever else might be requested?

, I don't remember why the uglify module was necessary, though I suspect redux-form wouldn't build properly without it.

I cleaned up the git instructions; thanks for noting that. co for checkout and ci for checkin/commit are left over from my CVS days last millenium.

Why is it necessary to yarn add uglifyjs-webpack-plugin?

BTW., your instructions say to use git co. I guess this an alias that you set up years ago and have got so used to using you don't even notice it any more, as I have done with git com for commit. But the instructions would be better and more explicit if you said to use git checkout.