Standardize Build Strategy

[curran]

Currently, there are several modules shimmed out of browser builds for each Chiasm component, but this is not documented anywhere. Also, the NPM scripts are different for each Chiasm subproject.

• Generate a "standard template" that includes NPM scripts
  • test - runs unit tests
  • build - creates the NPM build and the browser build
  • release - this script should help with the process of adding a specific version of the browser build to the gh-pages branch.

The current flow for cutting a release involves too much manual work:

npm version patch
npm publish
git push --tags
git push
npm run build-browser
cp chiasm-modue.js ../
git checkout gh-pages
mv ../chiasm-module.js ./chiasm-module-v0.2.1
git add .
git commit -m "Add v0.2.1"
git push

[Hypercubed]

Might conisder using np and p-s.

[curran]

Thanks, those look like awesome tools!