Using react-intl-redux package.
This just sets up the default English. Language switching in another PR. Requires locale/messages.json to exist, `{}` is ok.
Generate `locale/messages.json` from available languages in `translations`. If there are no translations for a given language (from `languages.json`) it just skips it, react-intl will use the default english strings.
Just using English, French and Spanish for testing right now.
Generating the localization source to update the translation system (transifex) is really separate from building. When building we want to be using the current state of translations from transifex, and the english default strings are not needed.
Uses the babel-cli to run the babel-plugin-react-intl separately from webpack.
Using babel-plugin-react intl to extract messages from sources that use react-intl. It creates one file per component, that’s not ideal for translators.
Transifex supports several different json formats. We picked the chrome i18n json format because it includes the ‘description’ and displays that to translators as instructions in the transifex UI.
In case the remote one gets deleted for some reason. I already had a fork of gh-pages, which is why I'm using rschamp rather than LLK. This is intended to be temporary.
Currently using an unmerged PR in gh-pages. (Will update to an LLK fork if we decide to go this way.)
Move to Travis build stages to handle the multiple deploy methods by branch.
Stop "testing" in more Node versions than 6, as this is basically just testing our build tools (using a single Node version simplifies using build stages.)
Also add a `watch` command for testing static build output.
Reverts #335.
Pinning to `^0.1.0.prerelease.0` is not equivalent to `latest`, since has the effect of not installing the latest version on `npm install`, you have to also do `npm update`. This hurts us ergonomically on `npm install`, and doesn't help us since we already are releasing breaking changes on `prerelease`.
chrisgarrity