* update scratch-l10n dependency
The new scratch-l10n package includes a script that will push the source file to transfex. Updated the package.json to push the source after extracting strings.
Travis deploy that will build and push strings if run as a cron job
* Fix package-lock
Ran `npm i` as suggested by failing travis log.
We have thought about moving to use package-lock.json the way NPM suggests, and at the same time have begun having issues with Travis caches. To address both at the same time, remove the cache from Travis, and make up the time by moving to package-lock.json + npm ci for install.
Now that the release stage is only created for master and develop, allow the deploy to run on any branch. This way we can control which branches get deployed from the stage condition alone.
This is something we want enabled for all builds, so it should be a global. This should simplify the matrix. The builds without an NPM_SCRIPT didn't do anything anyway.
The issues:
* The scratch-blocks@0.1.0 version exists because I accidentally published 0.1.0 (no -prerelease modifier) while setting up NPM
* I added a step that causes Travis to run `npm update` after installing
* The "0.1.0-prepublish" dependency version makes no sense
This made Travis install the old version of scratch-blocks that I published accidentally, which breaks the playground.
Don't output full logs, just the commit that the build is for. And use the author, not the committer, since GitHub is almost always the committer on develop.
This is the less hacky way to keep scratch-* packages up to date (and any others in the future). This is only necessary because we cache the node_modules directory.
With node_modules cached, npm install sees the scratch-* dependencies satisfied (since if any version 0.1.0-prepublish.x satisfies ^0.1.0-prepublish). So remove these before the install step to ensure the latest version is installed.
Authenticate with NPM via .npmrc and publish the package version + "-[git sha]".
Remove vm and vm.min.js, they'll be built before the package is published to NPM and available on installation. When installing from git, the build step will run on npm install.
