The webpack-md5-hash plugin attempts to make the generated hashes
less susceptible to churn when chunks haven't actually changed.
However it requires careful use and clearly wasn't set up correctly,
since the manifest file hashes were always the same regardless of
content, causing stale files and runtime errors in production.
Once Neutrino v6 is released, we can use its new in-built support
for caching to save having to implement this ourselves.
The only change is the move of `karma` from angular-toarrayfilter's
`dependencies` to `devDependencies`, which stops us unnecessarily
pulling in an ancient version of karma, and the resultant security
warnings.
Packages have been updated as follows:
* `angular*`: Latest patch version, since it doesn't follow semver.
* `react*`: Latest patch version, since in 15.5 some obtrusive
deprecation warnings were added, and `enzyme`'s peer-dependencies
need adjusting too.
* `enzyme`: Unchanged, since the newer minor version gives warnings.
* all other packages have been bumped to their latest minor version.
This was performed using:
```
sudo yarn global add npm-check-updates
ncu --upgrade --upgradeAll --semverLevel minor
ncu --upgrade --upgradeAll --semverLevel major --reject '/^(angular|react|enzyme).*/'
```
In addition, `karma-coverage-istanbul-reporter`, `taskcluster-client`
and `hawk` have been bumped to the latest major versions since their
changelogs don't show any breaking changes that impact us.
The lock file was then regenerated using:
```
rm -rf node_modules/ yarn.lock
yarn install --no-bin-links
```
At some point later we'll want to perform the more involved `angular*`,
`react*`, `enzyme`, `jquery` and `neutrino*` updates.
Since it's faster, deterministic and doesn't given obscure errors when
using `--no-bin-links` (which is required for both npm and yarn on
Windows hosts), and as such unblocks the work in bug 1343624.
Many of the commands are the same as with npm. See:
https://yarnpkg.com/en/docs/usage
Ed Morley
Shruti Jasoria
Casey Williams
Ed Morley